Triple
T1631911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BGP |
E35274
|
entity |
| Predicate | currentVersion |
P3698
|
FINISHED |
| Object | BGP-4 |
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: BGP-4 | Statement: [BGP, currentVersion, BGP-4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BGP-4 Context triple: [BGP, currentVersion, BGP-4]
-
A.
BGP-4+
BGP-4+ is an enhanced version of the Border Gateway Protocol designed to support routing for IPv6 networks.
-
B.
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.
-
C.
RFC 4271
RFC 4271 is the core Internet standards document that specifies the Border Gateway Protocol version 4 (BGP-4), which governs inter-domain routing between autonomous systems.
-
D.
OSPFv3
OSPFv3 is the version of the Open Shortest Path First routing protocol designed to operate over IPv6 networks, providing link-state routing and support for IPv6 addressing and features.
-
E.
OSPF
OSPF (Open Shortest Path First) is a widely used interior gateway routing protocol that employs link-state information to determine the most efficient path for data within an IP network.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a909f6ee1881908f0753a77a2c4665 |
completed | March 5, 2026, 4:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad6096584c81909ce50469f23a8a12 |
completed | March 8, 2026, 11:42 a.m. |
Created at: March 4, 2026, 7:28 p.m.