Triple
T1081733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BGP-4+ |
E23960
|
entity |
| Predicate | uses |
P98
|
FINISHED |
| Object |
Multiprotocol Extensions for BGP
Multiprotocol Extensions for BGP is an enhancement to the Border Gateway Protocol that enables it to carry routing information for multiple network layer protocols and address families beyond traditional IPv4 unicast.
|
E23960
|
NE FINISHED |
How this triple was built (4 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: Multiprotocol Extensions for BGP | Statement: [BGP-4+, uses, Multiprotocol Extensions for BGP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Multiprotocol Extensions for BGP Context triple: [BGP-4+, uses, Multiprotocol Extensions for BGP]
-
A.
BGP-4+
BGP-4+ is an enhanced version of the Border Gateway Protocol designed to support routing for IPv6 networks.
-
B.
BGP
BGP (Border Gateway Protocol) is the primary inter-domain routing protocol used to exchange routing information and determine paths between autonomous systems on the global Internet.
-
C.
IS-IS for IPv6
IS-IS for IPv6 is an extension of the IS-IS interior gateway routing protocol that enables dynamic routing and topology discovery in IPv6 networks.
-
D.
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
-
E.
RFC 8200
RFC 8200 is the Internet Engineering Task Force (IETF) standard that specifies the core protocol architecture and operation of Internet Protocol version 6 (IPv6).
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Multiprotocol Extensions for BGP Triple: [BGP-4+, uses, Multiprotocol Extensions for BGP]
Generated description
Multiprotocol Extensions for BGP is an enhancement to the Border Gateway Protocol that enables it to carry routing information for multiple network layer protocols and address families beyond traditional IPv4 unicast.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Multiprotocol Extensions for BGP Target entity description: Multiprotocol Extensions for BGP is an enhancement to the Border Gateway Protocol that enables it to carry routing information for multiple network layer protocols and address families beyond traditional IPv4 unicast.
-
A.
BGP-4+
chosen
BGP-4+ is an enhanced version of the Border Gateway Protocol designed to support routing for IPv6 networks.
-
B.
BGP
BGP (Border Gateway Protocol) is the primary inter-domain routing protocol used to exchange routing information and determine paths between autonomous systems on the global Internet.
-
C.
IS-IS for IPv6
IS-IS for IPv6 is an extension of the IS-IS interior gateway routing protocol that enables dynamic routing and topology discovery in IPv6 networks.
-
D.
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
-
E.
RFC 8200
RFC 8200 is the Internet Engineering Task Force (IETF) standard that specifies the core protocol architecture and operation of Internet Protocol version 6 (IPv6).
- F. None of above.
Provenance (5 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95d35888190a20593a278175df7 |
completed | March 1, 2026, 10:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac42affbac8190b6b16a1d726d0d35 |
completed | March 7, 2026, 3:22 p.m. |
| NEDg | Description generation | batch_69ac44a7a69c8190af5289f6e46d571a |
completed | March 7, 2026, 3:30 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ac451af1508190a55c037328b41931 |
completed | March 7, 2026, 3:32 p.m. |
Created at: March 1, 2026, 7:42 p.m.