Triple

T306676
Position Surface form Disambiguated ID Type / Status
Subject RFC 9112 E6318 entity
Predicate obsoletes P101 FINISHED
Object 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.
 E40362 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 7231 | Statement: [RFC 9112, obsoletes, RFC 7231]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 7231
Context triple: [RFC 9112, obsoletes, RFC 7231]
  • A. RFC 9110
    RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
  • B. RFC 6241
    RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
  • C. 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.
  • D. RFC 9112
    RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
  • E. RFC 9111
    RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
  • 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 7231
Triple: [RFC 9112, obsoletes, RFC 7231]
Generated description
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.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: RFC 7231
Target entity description: 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.
  • A. RFC 9110
    RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
  • B. RFC 6241
    RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
  • C. 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.
  • D. RFC 9112
    RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
  • E. RFC 9111
    RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
  • 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_69a3bc2353408190b7658595498895bb completed March 1, 2026, 4:10 a.m.
NEDg Description generation batch_69a3bc94ea2c8190b2a0c0bca7af5f94 completed March 1, 2026, 4:12 a.m.
NED2 Entity disambiguation (via description) batch_69a3bd0357088190a144c6c408804f30 completed March 1, 2026, 4:13 a.m.
Created at: Feb. 28, 2026, 1:06 p.m.