Triple
T300502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YANG modeling language |
E6186
|
entity |
| Predicate | usedIn |
P98
|
FINISHED |
| Object | NETCONF |
E6187
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: NETCONF | Statement: [YANG modeling language, usedIn, NETCONF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NETCONF Context triple: [YANG modeling language, usedIn, NETCONF]
-
A.
NETCONF
chosen
NETCONF is a network management protocol standardized by the IETF that provides mechanisms to install, manipulate, and delete configuration data on network devices using a structured, XML-based approach.
-
B.
RESTCONF
RESTCONF is a RESTful protocol defined by the IETF for accessing and managing configuration and operational data on network devices using YANG data models.
-
C.
YANG modeling language
YANG modeling language is a data modeling language used to define the structure and configuration of network devices and services, particularly in modern network management and automation systems.
-
D.
SNMP
SNMP (Simple Network Management Protocol) is a standard Internet protocol used to monitor, manage, and configure network devices such as routers, switches, and servers.
-
E.
Network Control Protocol
Network Control Protocol was an early host-to-host communication protocol that formed the basis of data transmission on the ARPANET before the adoption of TCP/IP.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2e9e6a8308190b9bd15310e324504 |
completed | Feb. 28, 2026, 1:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3aba14b0881908eb4f62ac9261d63 |
completed | March 1, 2026, 2:59 a.m. |
Created at: Feb. 28, 2026, 1:06 p.m.