Triple
T7858442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPX/SPX |
E182433
|
entity |
| Predicate | routingSupport |
P12563
|
FINISHED |
| Object | distance-vector 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: distance-vector routing | Statement: [IPX/SPX, routingSupport, distance-vector routing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routingSupport Context triple: [IPX/SPX, routingSupport, distance-vector routing]
-
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.
routingBasis
chosen
Indicates the principle or criterion used to determine how something is directed, routed, or assigned among possible paths or destinations.
-
C.
routerTypes
Indicates that one entity specifies or categorizes the types or kinds of routers associated with another entity.
-
D.
routeSystem
Indicates a transportation or communication network framework within which specific routes are organized, defined, or managed.
-
E.
route
Indicates that one entity serves as a path or course used to travel or move between locations 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb1a787c8c8190bcd9ed76cc7aa4c5 |
completed | March 31, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:52 p.m.