Triple

T20847112
Position Surface form Disambiguated ID Type / Status
Subject RFC 2865 E513257 entity
Predicate obsoletes P101 FINISHED
Object RFC 2138 NE NERFINISHED

How this triple was built (3 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 2138 | Statement: [RFC 2865, obsoletes, RFC 2138]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 2138
Context triple: [RFC 2865, obsoletes, RFC 2138]
  • A. RFC 2358
    RFC 2358 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces earlier specifications related to the Point-to-Point Protocol (PPP) and its associated network control protocols.
  • B. RFC 1831
    RFC 1831 is the Internet standard that defines the core protocol specification for ONC (Open Network Computing) Remote Procedure Call.
  • C. RFC 2813
    RFC 2813 is an Internet standards document that specifies the server-to-server protocol for the Internet Relay Chat (IRC) network.
  • D. RFC 1038
    RFC 1038 is an early Internet standards document that specifies experimental extensions to the IP protocol, particularly for security and related options.
  • 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.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 2138
Target entity description: RFC 2138 is an earlier IETF specification that originally defined the RADIUS authentication and authorization protocol before being superseded by RFC 2865.
  • A. RFC 2358
    RFC 2358 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces earlier specifications related to the Point-to-Point Protocol (PPP) and its associated network control protocols.
  • B. RFC 1831
    RFC 1831 is the Internet standard that defines the core protocol specification for ONC (Open Network Computing) Remote Procedure Call.
  • C. RFC 2813
    RFC 2813 is an Internet standards document that specifies the server-to-server protocol for the Internet Relay Chat (IRC) network.
  • D. RFC 1038
    RFC 1038 is an early Internet standards document that specifies experimental extensions to the IP protocol, particularly for security and related options.
  • 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 (2 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_69e0b4f4898081908209e58edb8f9c45 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c34ffb588190881953a0480b29a8 completed April 21, 2026, 12:22 a.m.
Created at: April 16, 2026, 12:43 p.m.