Triple
T7836110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IS-IS |
E181693
|
entity |
| Predicate | routingAlgorithmType |
P12563
|
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: [IS-IS, routingAlgorithmType, link-state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routingAlgorithmType Context triple: [IS-IS, routingAlgorithmType, link-state]
-
A.
routingProtocol
Indicates that one entity uses, implements, or is associated with a specific routing protocol to determine paths for forwarding data in a network.
-
B.
routerTypes
Indicates that one entity specifies or categorizes the types or kinds of routers associated with another entity.
-
C.
routeOptimization
Indicates the process of determining the most efficient path or sequence of paths between locations according to specified criteria such as distance, time, or cost.
-
D.
routingBasis
chosen
Indicates the principle or criterion used to determine how something is directed, routed, or assigned among possible paths or destinations.
-
E.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
- 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb064cb7e081909e88419863d94dfe |
completed | March 30, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:46 p.m.