Triple

T1932770
Position Surface form Disambiguated ID Type / Status
Subject RFC 7233 E40982 entity
Predicate defines P264 FINISHED
Object If-Range header field
The If-Range header field is an HTTP request header that allows a client to conditionally request a range of a resource only if it has not changed since a specified validator (such as an ETag or date).
 E40465 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: If-Range header field | Statement: [RFC 7233, defines, If-Range header field]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: If-Range header field
Context triple: [RFC 7233, defines, If-Range header field]
  • A. If-None-Match
    If-None-Match is an HTTP request header used for conditional requests, typically with ETags, to perform cache validation or conditional updates without unnecessarily transferring data.
  • B. 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.
  • C. 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.
  • D. RFC 7234
    RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
  • E. 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.
  • 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: If-Range header field
Triple: [RFC 7233, defines, If-Range header field]
Generated description
The If-Range header field is an HTTP request header that allows a client to conditionally request a range of a resource only if it has not changed since a specified validator (such as an ETag or date).
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: If-Range header field
Target entity description: The If-Range header field is an HTTP request header that allows a client to conditionally request a range of a resource only if it has not changed since a specified validator (such as an ETag or date).
  • A. If-None-Match
    If-None-Match is an HTTP request header used for conditional requests, typically with ETags, to perform cache validation or conditional updates without unnecessarily transferring data.
  • B. 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.
  • C. RFC 7232 chosen
    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.
  • D. RFC 7234
    RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
  • E. 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.
  • 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_69a8864711648190b07bed24ed76258e completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb299f3c48190a5021d320ded4405 completed March 7, 2026, 5:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69adf3f16d0c8190967862b68e6cc373 completed March 8, 2026, 10:10 p.m.
NEDg Description generation batch_69adf484b6788190a678a05a52da7eda completed March 8, 2026, 10:13 p.m.
NED2 Entity disambiguation (via description) batch_69adf4f8f3c481909efcb6d632522e1a completed March 8, 2026, 10:15 p.m.
Created at: March 4, 2026, 7:35 p.m.