Triple
T1081728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BGP-4+ |
E23960
|
entity |
| Predicate | extends |
P1244
|
FINISHED |
| Object | Border Gateway Protocol |
E35274
|
NE 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: Border Gateway Protocol | Statement: [BGP-4+, extends, Border Gateway Protocol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Border Gateway Protocol Context triple: [BGP-4+, extends, Border Gateway Protocol]
-
A.
BGP
chosen
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.
-
B.
IPsec
IPsec is a suite of protocols that provides secure, encrypted communication over IP networks by authenticating and protecting the integrity and confidentiality of data packets.
-
C.
BCP 38
BCP 38 is an Internet Engineering Task Force (IETF) Best Current Practice that recommends network ingress filtering to prevent IP address spoofing and reduce the impact of denial-of-service attacks.
-
D.
BGP-4+
BGP-4+ is an enhanced version of the Border Gateway Protocol designed to support routing for IPv6 networks.
-
E.
Teredo
Teredo is a tunneling protocol that enables IPv6 connectivity for devices on IPv4 networks, particularly those behind NAT.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_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. |
Created at: March 1, 2026, 7:42 p.m.