Triple
T5678712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 10589 |
E125148
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Routing protocol specification |
C901
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Routing protocol specification Context triple: [ISO 10589, instanceOf, Routing protocol specification]
-
A.
path vector protocol
A path vector protocol is a type of routing protocol that advertises network reachability information along with the full path (sequence of autonomous systems or routers) to each destination, enabling loop avoidance and policy-based routing decisions.
-
B.
extension of BGP-4
An extension of BGP-4 is an enhancement to the Border Gateway Protocol version 4 that introduces additional capabilities—such as new address families, attributes, or policy mechanisms—while preserving interoperability with the base protocol.
-
C.
network protocol
chosen
A network protocol is a standardized set of rules and formats that enable computers and devices to communicate and exchange data reliably over a network.
-
D.
packet-switched protocol
A packet-switched protocol is a communication method that breaks data into discrete packets, routes them independently across a network, and reassembles them at the destination for efficient and robust data transfer.
-
E.
network layer protocol
A network layer protocol defines the rules and mechanisms for routing and forwarding data packets across interconnected networks, providing logical addressing and path selection between source and destination hosts.
- F. None of above.
Provenance (1 batch)
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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:44 p.m.