Triple

T5770867
Position Surface form Disambiguated ID Type / Status
Subject RFC 5340 E127327 entity
Predicate defines P264 FINISHED
Object OSPFv3 E23866 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: OSPFv3 | Statement: [RFC 5340, defines, OSPFv3]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: OSPFv3
Context triple: [RFC 5340, defines, OSPFv3]
  • A. OSPFv3 chosen
    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.
  • B. 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.
  • C. BGP-4+
    BGP-4+ is an enhanced version of the Border Gateway Protocol designed to support routing for IPv6 networks.
  • D. 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.
  • E. EIGRP
    EIGRP (Enhanced Interior Gateway Routing Protocol) is a Cisco-developed advanced distance-vector routing protocol used to efficiently route IP traffic within large enterprise 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_69c00834f6308190851b0abeddd8ed7e completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c029ac21ec81908d88ba72e966d7cb completed March 22, 2026, 5:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69c09809cfcc8190b4d55db4b74316c7 completed March 23, 2026, 1:31 a.m.
Created at: March 22, 2026, 3:50 p.m.