Triple
T300487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YANG modeling language |
E6186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | data modeling language |
C845
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: data modeling language Context triple: [YANG modeling language, instanceOf, data modeling language]
-
A.
YANG data model standard
chosen
A YANG data model standard is a formal, structured language used to model configuration and state data for network devices and services in a vendor-neutral, interoperable way.
-
B.
theoretical model
A theoretical model is an abstract, simplified representation of a system or phenomenon used to explain, predict, or understand its behavior based on underlying principles and assumptions.
-
C.
controlled vocabulary
A controlled vocabulary is a standardized, curated set of terms and phrases used consistently to describe and organize information, ensuring uniformity and improving search and retrieval.
-
D.
formal language classification scheme
A formal language classification scheme is a systematic framework for categorizing formal languages based on their generative or recognitional power, typically using hierarchies such as the Chomsky hierarchy.
-
E.
bibliographic authority data set
A bibliographic authority data set is a structured collection of standardized records that uniquely identify and describe entities (such as persons, organizations, works, and subjects) used to control and link names and headings in bibliographic and library catalogs.
- F. None of above.
Provenance (1 batch)
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. |
Created at: Feb. 28, 2026, 1:06 p.m.