Triple

T1814064
Position Surface form Disambiguated ID Type / Status
Subject RFC 3410 E40395 entity
Predicate obsoletes P101 FINISHED
Object RFC 1909
RFC 1909 is an older Internet Engineering Task Force (IETF) Request for Comments document that was later superseded by RFC 3410 as part of the evolution of network management standards.
E276198 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 1909 | Statement: [RFC 3410, obsoletes, RFC 1909]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 1909
Context triple: [RFC 3410, obsoletes, RFC 1909]
  • A. 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.
  • B. RFC 1659
    RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
  • C. RFC 1908
    RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
  • D. RFC 1904
    RFC 1904 is an Internet standards document that originally defined the textual conventions for SNMPv2 before later being superseded by RFC 3410.
  • E. RFC 1592
    RFC 1592 is an early Internet standards document that specified procedures and mechanisms related to network management and operations before being superseded by later RFCs.
  • 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 1909
Triple: [RFC 3410, obsoletes, RFC 1909]
Generated description
RFC 1909 is an older Internet Engineering Task Force (IETF) Request for Comments document that was later superseded by RFC 3410 as part of the evolution of network management standards.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 1909
Target entity description: RFC 1909 is an older Internet Engineering Task Force (IETF) Request for Comments document that was later superseded by RFC 3410 as part of the evolution of network management standards.
  • A. 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.
  • B. RFC 1659
    RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
  • C. RFC 1908
    RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
  • D. RFC 1904
    RFC 1904 is an Internet standards document that originally defined the textual conventions for SNMPv2 before later being superseded by RFC 3410.
  • E. RFC 1592
    RFC 1592 is an early Internet standards document that specified procedures and mechanisms related to network management and operations before being superseded by later RFCs.
  • 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_69a8864526c081908a3a4d74f689e2c5 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa65c905ec8190bea7cd72d218487a completed March 6, 2026, 5:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69af5cb503bc8190823a843bb58d85e1 completed March 9, 2026, 11:50 p.m.
NEDg Description generation batch_69af5d4795288190bb09c1a928e70b3e completed March 9, 2026, 11:52 p.m.
NED2 Entity disambiguation (via description) batch_69af5dca88948190b0b195bce7126891 completed March 9, 2026, 11:54 p.m.
Created at: March 4, 2026, 7:32 p.m.