Triple
T21802572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LSP PDU |
E538272
|
entity |
| Predicate | usedInRoutingType |
P64008
|
FINISHED |
| Object | link-state routing |
—
|
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 routing | Statement: [LSP PDU, usedInRoutingType, link-state routing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInRoutingType Context triple: [LSP PDU, usedInRoutingType, link-state routing]
-
A.
usesRoutingType
chosen
Indicates that one entity employs or operates according to a specific routing type or routing method associated with another entity.
-
B.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
C.
usedRoutes
Indicates that an entity has utilized or traveled along specific routes.
-
D.
currentUseOfRoute
Indicates that a particular route is presently being used for a specific purpose, activity, or traffic flow.
-
E.
includesRouteType
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0780062688190a6c3a2a0364f0f77 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.