Triple

T10623784
Position Surface form Disambiguated ID Type / Status
Subject RFC 2026 E250269 entity
Predicate obsoletes P101 FINISHED
Object RFC 1602
RFC 1602 was an earlier Internet standards process document that defined procedures for developing and standardizing Internet protocols before being superseded by RFC 2026.
 E877062 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 1602 | Statement: [RFC 2026, obsoletes, RFC 1602]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 1602
Context triple: [RFC 2026, obsoletes, RFC 1602]
  • A. 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.
  • B. RFC 1642
    RFC 1642 is an Internet standards document that defines the UTF-7 encoding for representing Unicode characters in environments restricted to 7-bit data.
  • C. 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.
  • D. RFC 1670
    RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
  • 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 1602
Triple: [RFC 2026, obsoletes, RFC 1602]
Generated description
RFC 1602 was an earlier Internet standards process document that defined procedures for developing and standardizing Internet protocols before being superseded by RFC 2026.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: RFC 1602
Target entity description: RFC 1602 was an earlier Internet standards process document that defined procedures for developing and standardizing Internet protocols before being superseded by RFC 2026.
  • A. 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.
  • B. RFC 1642
    RFC 1642 is an Internet standards document that defines the UTF-7 encoding for representing Unicode characters in environments restricted to 7-bit data.
  • C. 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.
  • D. RFC 1670
    RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
  • 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_69d6aa5993448190a493b790b8f85010 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6df7f11fc8190aed858f2e1443c08 completed April 8, 2026, 11:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69d97a356e548190ab7a4a2c7111ba89 completed April 10, 2026, 10:31 p.m.
NEDg Description generation batch_69d97cc07100819088683a0d79b2baa0 completed April 10, 2026, 10:42 p.m.
NED2 Entity disambiguation (via description) batch_69d97e015b088190a97822675eecaa5a completed April 10, 2026, 10:47 p.m.
Created at: April 8, 2026, 8:52 p.m.