Triple
T5479454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSPF |
E123434
|
entity |
| Predicate | usesRoutingType |
P64008
|
FINISHED |
| Object | link-state |
—
|
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: link-state | Statement: [OSPF, usesRoutingType, link-state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRoutingType Context triple: [OSPF, usesRoutingType, link-state]
-
A.
supportsRouting
Indicates that one entity provides the capability to determine and direct paths or routes for another entity’s traffic, requests, or messages.
-
B.
includesRouteType
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
-
C.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
D.
usedByRegimeType
Indicates that something (such as a method, policy, or tool) is employed or implemented by a particular type of political regime.
-
E.
parentRouteType
Indicates that one route type serves as the parent or higher-level category for another route type within a route hierarchy.
- F. None of above. chosen
Provenance (4 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd9214b8488190979112c7615f359a |
completed | March 20, 2026, 6:29 p.m. |
Created at: March 20, 2026, 2:09 p.m.