Triple
T300614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RESTCONF |
E6188
|
entity |
| Predicate | relationshipToNETCONF |
P845
|
FINISHED |
| Object | provides RESTful interface to NETCONF/YANG data |
—
|
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: provides RESTful interface to NETCONF/YANG data | Statement: [RESTCONF, relationshipToNETCONF, provides RESTful interface to NETCONF/YANG data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToNETCONF Context triple: [RESTCONF, relationshipToNETCONF, provides RESTful interface to NETCONF/YANG data]
-
A.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
B.
definesRelationshipBetween
Indicates that one entity specifies or establishes the nature, type, or rules of a relationship that exists between two or more other entities.
-
C.
connectsTo
chosen
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
D.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
E.
peerOf
Indicates that two entities hold equivalent or comparable status, role, or standing within the same context or system.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea2fba548190a5aeb1597dca96bd |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93aff048190a633c8ae2b76a41f |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.