Triple

T5478989
Position Surface form Disambiguated ID Type / Status
Subject RFC 2460 E123424 entity
Predicate replaces P101 FINISHED
Object RFC 1883
RFC 1883 is the original Internet standard that defined the IPv6 protocol header format and core mechanisms before being superseded by RFC 2460.
 E522208 NE FINISHED

How this triple was built (4 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: RFC 1883 | Statement: [RFC 2460, replaces, RFC 1883]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 1883
Context triple: [RFC 2460, replaces, RFC 1883]
  • A. RFC 1813
    RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
  • B. RFC 1908
    RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
  • C. RFC 1939
    RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
  • D. RFC 1664
    RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
  • E. RFC 1869
    RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 1883
Triple: [RFC 2460, replaces, RFC 1883]
Generated description
RFC 1883 is the original Internet standard that defined the IPv6 protocol header format and core mechanisms before being superseded by RFC 2460.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: RFC 1883
Target entity description: RFC 1883 is the original Internet standard that defined the IPv6 protocol header format and core mechanisms before being superseded by RFC 2460.
  • A. RFC 1813
    RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
  • B. RFC 1908
    RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
  • C. RFC 1939
    RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
  • D. RFC 1664
    RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
  • E. RFC 1869
    RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
  • F. None of above. chosen

Provenance (5 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_69bd4648883481909e9775d43300c5fa completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd9247a16c8190ac5a02534da48853 completed March 20, 2026, 6:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf48a001c081909b0e9f1b36fd10db completed March 22, 2026, 1:40 a.m.
NEDg Description generation batch_69bf496861f08190aca539510ddfebbc completed March 22, 2026, 1:44 a.m.
NED2 Entity disambiguation (via description) batch_69bf49c564188190b4b3a40ee09b0461 completed March 22, 2026, 1:45 a.m.
Created at: March 20, 2026, 2:09 p.m.