Triple

T394785
Position Surface form Disambiguated ID Type / Status
Subject RFC 9114 E8958 entity
Predicate references P771 FINISHED
Object HTTP Semantics
HTTP Semantics is the IETF specification that defines the core concepts, methods, status codes, and header fields that govern how the Hypertext Transfer Protocol behaves independently of any particular transport.
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: HTTP Semantics | Statement: [RFC 9114, references, HTTP Semantics]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HTTP Semantics
Context triple: [RFC 9114, references, HTTP Semantics]
  • A. HTTP
    HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
  • B. RFC 7230
    RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
  • C. 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.
  • D. RFC 7235
    RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
  • E. 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.
  • 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: HTTP Semantics
Triple: [RFC 9114, references, HTTP Semantics]
Generated description
HTTP Semantics is the IETF specification that defines the core concepts, methods, status codes, and header fields that govern how the Hypertext Transfer Protocol behaves independently of any particular transport.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: HTTP Semantics
Target entity description: HTTP Semantics is the IETF specification that defines the core concepts, methods, status codes, and header fields that govern how the Hypertext Transfer Protocol behaves independently of any particular transport.
  • A. HTTP
    HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
  • B. RFC 7230
    RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
  • C. RFC 7231 chosen
    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.
  • D. RFC 7235
    RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
  • E. 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.
  • F. None of above.

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_69a2e7f55c60819097aff65ea2ca2832 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec77a8a08190b6f96373aa8c1346 completed Feb. 28, 2026, 1:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69a405fa43448190b3e78d83e791b105 completed March 1, 2026, 9:25 a.m.
NEDg Description generation batch_69a4070f76308190bd898dcdb27f3277 completed March 1, 2026, 9:29 a.m.
NED2 Entity disambiguation (via description) batch_69a40794523081908839f90446beba83 completed March 1, 2026, 9:32 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.