Triple
T10216666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1657 |
E242461
|
entity |
| Predicate | protocol |
P1992
|
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: [RFC 1657, protocol, BGP-4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BGP-4 Context triple: [RFC 1657, protocol, 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.
RSVP-TE
RSVP-TE is a signaling protocol used in MPLS networks to establish and manage traffic-engineered label-switched paths with specific resource and QoS constraints.
-
E.
RFC 2328
RFC 2328 is the Internet Engineering Task Force (IETF) standard that specifies version 2 of the Open Shortest Path First (OSPFv2) interior gateway routing protocol used in IP networks.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa6e544c8190961cdd7f1fbe24e6 |
completed | April 6, 2026, 12:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6a804e8748190b4ebcfa9a0bb889f |
completed | April 8, 2026, 7:09 p.m. |
Created at: April 6, 2026, 11:06 a.m.