Triple

T1777484
Position Surface form Disambiguated ID Type / Status
Subject RFC 1901 E39212 entity
Predicate obsoletes P101 FINISHED
Object RFC 1654
RFC 1654 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for transmitting network layer datagrams over serial point-to-point links.
E235766 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 1654 | Statement: [RFC 1901, obsoletes, RFC 1654]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 1654
Context triple: [RFC 1901, obsoletes, RFC 1654]
  • 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 1653
    RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
  • C. RFC 4954
    RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
  • D. RFC 3414
    RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
  • E. RFC 1651
    RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
  • 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 1654
Triple: [RFC 1901, obsoletes, RFC 1654]
Generated description
RFC 1654 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for transmitting network layer datagrams over serial point-to-point links.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 1654
Target entity description: RFC 1654 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for transmitting network layer datagrams over serial point-to-point links.
  • 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 1653
    RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
  • C. RFC 4954
    RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
  • D. RFC 3414
    RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
  • E. RFC 1651
    RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
  • 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_69ae516bbbf48190ae87ec3344da64d1 completed March 9, 2026, 4:49 a.m.
NEDg Description generation batch_69ae5209ae40819095e02cafb8112a1f completed March 9, 2026, 4:52 a.m.
NED2 Entity disambiguation (via description) batch_69ae529375788190aead19ec0874f11e completed March 9, 2026, 4:54 a.m.
Created at: March 4, 2026, 7:31 p.m.