Triple
T1869560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF NETCONF Working Group |
E39002
|
entity |
| Predicate | usesDataModelingLanguage |
P535
|
FINISHED |
| Object | YANG |
—
|
LITERAL 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: YANG | Statement: [IETF NETCONF Working Group, usesDataModelingLanguage, YANG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDataModelingLanguage Context triple: [IETF NETCONF Working Group, usesDataModelingLanguage, YANG]
-
A.
dataModel
chosen
Indicates a relationship where an entity defines, uses, or is structured according to a specific data model or schema.
-
B.
usedProgramModel
Indicates that an entity employed a specific program model as the basis or framework for its activities or operations.
-
C.
usesDialect
Indicates that one entity communicates or expresses itself using the specific dialect associated with another entity.
-
D.
usesDataStructure
Indicates that one entity employs or relies on a particular data structure in its operation or implementation.
-
E.
isModelOf
Indicates that one entity serves as a representation or abstraction that captures the structure or behavior of another entity.
- F. None of above.
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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe02c3c819093a4744b476106ca |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.