Triple

T306678
Position Surface form Disambiguated ID Type / Status
Subject RFC 9112 E6318 entity
Predicate obsoletes P101 FINISHED
Object RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
 E40982 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 7233 | Statement: [RFC 9112, obsoletes, RFC 7233]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 7233
Context triple: [RFC 9112, obsoletes, RFC 7233]
  • A. RFC 7232
    RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
  • B. RFC 7231
    RFC 7231 is an IETF specification that defined the semantics and content of the HTTP/1.1 protocol, including methods, status codes, and header fields, before being superseded by RFC 9112.
  • C. RFC 9110
    RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
  • D. RFC 9113
    RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
  • E. RFC 7950
    RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
  • 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 7233
Triple: [RFC 9112, obsoletes, RFC 7233]
Generated description
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: RFC 7233
Target entity description: RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
  • A. RFC 7232
    RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
  • B. RFC 7231
    RFC 7231 is an IETF specification that defined the semantics and content of the HTTP/1.1 protocol, including methods, status codes, and header fields, before being superseded by RFC 9112.
  • C. RFC 9110
    RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
  • D. RFC 9113
    RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
  • E. RFC 7950
    RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
  • 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_69a2e79230508190b912ecb555aae17e completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2ea313be88190b4441f3ea41a99e2 completed Feb. 28, 2026, 1:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3c8b480388190b5f7f9e11479de91 completed March 1, 2026, 5:03 a.m.
NEDg Description generation batch_69a3c91e8b88819099e54b7869cc293d completed March 1, 2026, 5:05 a.m.
NED2 Entity disambiguation (via description) batch_69a3c9731df881908e342ace3635b5cc completed March 1, 2026, 5:06 a.m.
Created at: Feb. 28, 2026, 1:06 p.m.