Triple

T7987470
Position Surface form Disambiguated ID Type / Status
Subject RFC 2119 E185717 entity
Predicate obsoletes P101 FINISHED
Object RFC 1123 (terminology portions) E184138 NE FINISHED

How this triple was built (2 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 1123 (terminology portions) | Statement: [RFC 2119, obsoletes, RFC 1123 (terminology portions)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 1123 (terminology portions)
Context triple: [RFC 2119, obsoletes, RFC 1123 (terminology portions)]
  • A. RFC 1123 chosen
    RFC 1123 is an Internet standards document that refines and extends the requirements for host software, including DNS and related protocols, to ensure interoperability on the early Internet.
  • B. RFC 1034
    RFC 1034 is an Internet standards document that specifies the concepts and facilities of the Domain Name System (DNS), defining how domain names are structured and resolved on the internet.
  • C. RFC 5322
    RFC 5322 is the Internet standard that defines the syntax and format of text-based email messages, including headers such as From, To, Subject, and Date.
  • D. RFC 4513
    RFC 4513 is an IETF standard that specifies authentication methods and security mechanisms for the Lightweight Directory Access Protocol (LDAP).
  • E. RFC 2131
    RFC 2131 is the Internet Engineering Task Force (IETF) standard that specifies the Dynamic Host Configuration Protocol (DHCP) used for automatic IP address and configuration assignment in IP networks.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca829a2cfc819083d591d58ec04075 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3c4d11b08190aa13afb17155462c completed March 31, 2026, 3:15 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbe0ed61588190b01423061acfce49 completed March 31, 2026, 2:57 p.m.
Created at: March 30, 2026, 5:15 p.m.