Triple

T1866840
Position Surface form Disambiguated ID Type / Status
Subject RFC 5321 E34940 entity
Predicate obsoletes P101 FINISHED
Object 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.
 E280627 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 1869 | Statement: [RFC 5321, obsoletes, RFC 1869]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 1869
Context triple: [RFC 5321, obsoletes, RFC 1869]
  • A. 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.
  • B. 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.
  • C. RFC 1668
    RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
  • D. 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.
  • E. RFC 1908
    RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
  • 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 1869
Triple: [RFC 5321, obsoletes, RFC 1869]
Generated description
RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: RFC 1869
Target entity description: RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
  • A. 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.
  • B. 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.
  • C. RFC 1668
    RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
  • D. 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.
  • E. RFC 1908
    RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
  • 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_69a88600b2f88190bc09303e68ab517e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abb0b5978c81909390f2cbd716ccaf completed March 7, 2026, 4:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69af8336f98c8190949c0145d2d31a8f completed March 10, 2026, 2:34 a.m.
NEDg Description generation batch_69af840b2fb881909755b06563b8c561 completed March 10, 2026, 2:38 a.m.
NED2 Entity disambiguation (via description) batch_69af8487bcac819085b6f5827a48696a completed March 10, 2026, 2:40 a.m.
Created at: March 4, 2026, 7:34 p.m.