Triple

T9690784
Position Surface form Disambiguated ID Type / Status
Subject RFC 5905 E234528 entity
Predicate obsoletes P101 FINISHED
Object RFC 1769
RFC 1769 is an older Internet standard that specified the Simple Network Time Protocol (SNTP) for clock synchronization over IP networks.
 E815697 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 1769 | Statement: [RFC 5905, obsoletes, RFC 1769]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 1769
Context triple: [RFC 5905, obsoletes, RFC 1769]
  • A. 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.
  • 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 1667
    RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
  • D. RFC 1660
    RFC 1660 is an early Internet standards document that specified an initial version of the Simple Network Management Protocol (SNMP) over OSI transport services before being superseded by later RFCs.
  • E. RFC 1657
    RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
  • 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 1769
Triple: [RFC 5905, obsoletes, RFC 1769]
Generated description
RFC 1769 is an older Internet standard that specified the Simple Network Time Protocol (SNTP) for clock synchronization over IP networks.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: RFC 1769
Target entity description: RFC 1769 is an older Internet standard that specified the Simple Network Time Protocol (SNTP) for clock synchronization over IP networks.
  • A. 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.
  • 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 1667
    RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
  • D. RFC 1660
    RFC 1660 is an early Internet standards document that specified an initial version of the Simple Network Management Protocol (SNMP) over OSI transport services before being superseded by later RFCs.
  • E. RFC 1657
    RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
  • 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_69ca84ca73208190957a900c8543bdcc completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9d0422e88190a234ba74eb0dad25 completed April 1, 2026, 10:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69d19118874c81909a97f874b1dc2db8 completed April 4, 2026, 10:30 p.m.
NEDg Description generation batch_69d193a5cdac8190b84564f397d00124 completed April 4, 2026, 10:41 p.m.
NED2 Entity disambiguation (via description) batch_69d19457c6488190a7bc72e1a27c088a completed April 4, 2026, 10:44 p.m.
Created at: March 30, 2026, 8:17 p.m.