Triple

T1077017
Position Surface form Disambiguated ID Type / Status
Subject RFC 8200 E23862 entity
Predicate title P38 FINISHED
Object Internet Protocol, Version 6 (IPv6) Specification E4018 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: Internet Protocol, Version 6 (IPv6) Specification | Statement: [RFC 8200, title, Internet Protocol, Version 6 (IPv6) Specification]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Internet Protocol, Version 6 (IPv6) Specification
Context triple: [RFC 8200, title, Internet Protocol, Version 6 (IPv6) Specification]
  • A. Internet Protocol version 6 chosen
    Internet Protocol version 6 (IPv6) is the modern Internet addressing and routing protocol designed to replace IPv4 by providing a vastly larger address space and improved network efficiency and security features.
  • B. 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).
  • 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. RFC 3410
    RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
  • E. RFC 6176
    RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
  • 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_69a4b940d4848190930e73597afd1fcf completed March 1, 2026, 10:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac42abc7a08190a34f5b2d393db30e completed March 7, 2026, 3:22 p.m.
Created at: March 1, 2026, 7:42 p.m.