Triple

T8486757
Position Surface form Disambiguated ID Type / Status
Subject Date (HTTP header) E200849 entity
Predicate relatedTo P37 FINISHED
Object Last-Modified (HTTP header)
Last-Modified is an HTTP response header that indicates the date and time at which the origin server believes the requested resource was last changed, enabling caching and conditional requests.
 E736181 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: Last-Modified (HTTP header) | Statement: [Date (HTTP header), relatedTo, Last-Modified (HTTP header)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Last-Modified (HTTP header)
Context triple: [Date (HTTP header), relatedTo, Last-Modified (HTTP header)]
  • 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 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.
  • C. 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.
  • 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: Last-Modified (HTTP header)
Triple: [Date (HTTP header), relatedTo, Last-Modified (HTTP header)]
Generated description
Last-Modified is an HTTP response header that indicates the date and time at which the origin server believes the requested resource was last changed, enabling caching and conditional requests.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Last-Modified (HTTP header)
Target entity description: Last-Modified is an HTTP response header that indicates the date and time at which the origin server believes the requested resource was last changed, enabling caching and conditional requests.
  • 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 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.
  • C. 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.
  • 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

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_69ca831d7b148190a6e32c1de43ab13b completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe53c4d608190a766c0e919a4b96f completed March 31, 2026, 3:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce3a45e30c8190838ac499bbc66fbd completed April 2, 2026, 9:43 a.m.
NEDg Description generation batch_69ce3c22f3c0819084803630d438c55e completed April 2, 2026, 9:51 a.m.
NED2 Entity disambiguation (via description) batch_69ce3ca57ec081909a14d962eee2c9a5 completed April 2, 2026, 9:53 a.m.
Created at: March 30, 2026, 6:13 p.m.