Triple

T7928140
Position Surface form Disambiguated ID Type / Status
Subject RFC 6856 E184118 entity
Predicate obsoletesStatusOf P58063 FINISHED
Object RFC 5721 E700350 NE FINISHED

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 5721 | Statement: [RFC 6856, obsoletesStatusOf, RFC 5721]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 5721
Context triple: [RFC 6856, obsoletesStatusOf, RFC 5721]
  • A. RFC 5721 chosen
    RFC 5721 was an Internet standards document that defined an earlier approach to email-related functionality before being superseded by RFC 6856.
  • B. RFC 5741
    RFC 5741 is an Internet Engineering Task Force (IETF) document that defines the structure, responsibilities, and processes governing the IETF document publication streams.
  • C. RFC 5661
    RFC 5661 is the Internet Engineering Task Force (IETF) standard that specifies version 4.1 of the Network File System (NFS) protocol, detailing its architecture, operations, and extensions for distributed file access.
  • D. RFC 5751
    RFC 5751 is the Internet standards document that specifies the Secure/Multipurpose Internet Mail Extensions (S/MIME) protocol for secure email communication.
  • E. RFC 5702
    RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: obsoletesStatusOf
Context triple: [RFC 6856, obsoletesStatusOf, RFC 5721]
  • A. wasSupersededBy
    Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
  • B. statusAfterSupersession chosen
    Indicates the status or condition an entity holds after it has been superseded by another entity.
  • C. abolishedInEffectBy
    Indicates that the legal force or practical operation of something is nullified or terminated as a result of another specified action or measure.
  • D. eraOfObsolescence
    Indicates the time period during which something becomes outdated, no longer useful, or superseded by newer alternatives.
  • E. discontinuedInFavorOf
    Indicates that one thing has been stopped, ended, or phased out specifically so it can be replaced by another preferred alternative.
  • F. None of above.

Provenance (4 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_69ca828fe7bc819090f52c88dcd72183 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3ac9ac4c819082cd2190fc3ce5a2 completed March 31, 2026, 3:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbe011ccec8190ab60d18b761666af completed March 31, 2026, 2:54 p.m.
PD Predicate disambiguation batch_69cae9335f288190ba96781fd6576a2b completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 5:07 p.m.