The template-mappings represent the low-level, device-specific configuration that the Nokia NSP system generates by translating a high-level, abstract intent. This mapping is a direct result of the intent's realization and is unique to each specific intent instance. This operational data is not part of the original intent definition or the general data model. Consequently, it can only be inspected by performing a RESTCONF GET request on a specific, existing intent to view its operational state and see how it was translated into concrete configurations.

A. abstract YANG model: This is a schema, not instance-specific data. It defines the structure for a type of intent and is retrieved from the system's YANG library, not from a single intent instance.

B. ibn:intent model: This is the specific YANG model for the intent-based networking framework. Like any YANG model, it is a definition and is not retrieved by querying an existing data instance.

D. metadata: Metadata, such as the intent's name or description, is part of the intent's configuration. While it is viewed by querying the intent, it is often also visible in summary lists or other high-level views, not only through a specific RESTCONF query.

1. Nokia Network Services Platform (NSP) Intent Manager REST API Developer Guide: This guide details the RESTCONF API for managing intents. It shows that a GET request on an existing intent (/restconf/data/nsp-intent:intents/intent={intent-id}) returns a payload containing various fields. The template-mappings field is shown as part of the operational data returned for a specific, realized intent, detailing the templates used to generate the device configuration. This information is not available elsewhere. (Consult specific version of the guide for exact field names and API paths).

2. Nokia Network Services Platform (NSP) Intent-Based Networking Guide, Release 22.10, Section: "Intent lifecycle and operational states": This document explains that as an intent moves from a requested state to a realized state, the NSP's Intent Manager processes it, applying templates to generate device-level configurations. The record of this translation (the template mappings) becomes part of the intent's operational state, which is queryable per-intent.

3. RFC 8342, "Network Management Datastore Architecture (NMDA)", Section 3.1: This IETF standard, which underpins systems like NSP, distinguishes between configuration datastores (, ) and operational state datastores (). The template-mappings are operational state data, derived by the system, whereas metadata is typically configuration data. This distinction supports that operational details are inspected from the specific managed node (in this case, the intent instance).