Triple

T1777497
Position Surface form Disambiguated ID Type / Status
Subject RFC 1901 E39212 entity
Predicate obsoletes P101 FINISHED
Object RFC 1667
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
 E263365 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 1667 | Statement: [RFC 1901, obsoletes, RFC 1667]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 1667
Context triple: [RFC 1901, obsoletes, RFC 1667]
  • A. 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.
  • B. RFC 1666
    RFC 1666 is an early Internet standards document that was later superseded by RFC 1901 as the protocol or specification it defined evolved.
  • C. RFC 1665
    RFC 1665 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
  • D. RFC 1652
    RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
  • E. 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.
  • 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 1667
Triple: [RFC 1901, obsoletes, RFC 1667]
Generated description
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: RFC 1667
Target entity description: RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
  • A. 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.
  • B. RFC 1666
    RFC 1666 is an early Internet standards document that was later superseded by RFC 1901 as the protocol or specification it defined evolved.
  • C. RFC 1665
    RFC 1665 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
  • D. RFC 1652
    RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
  • E. 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.
  • 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_69a88630519c8190a17addd83c4a3ef4 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa64b967f08190a73216361b9c2d83 completed March 6, 2026, 5:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69aeb3a777a481909e8b350811ee29c0 completed March 9, 2026, 11:48 a.m.
NEDg Description generation batch_69aeb48dfbfc81908193c909315bd030 completed March 9, 2026, 11:52 a.m.
NED2 Entity disambiguation (via description) batch_69aeb57af28c8190bfca30ad3e7ca8b3 completed March 9, 2026, 11:56 a.m.
Created at: March 4, 2026, 7:31 p.m.