Triple
T8486758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Date (HTTP header) |
E200849
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Cache-Control (HTTP header) |
E60792
|
NE FINISHED |
How this triple was built (2 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: Cache-Control (HTTP header) | Statement: [Date (HTTP header), relatedTo, Cache-Control (HTTP header)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cache-Control (HTTP header) Context triple: [Date (HTTP header), relatedTo, Cache-Control (HTTP header)]
-
A.
HTTP Caching
HTTP Caching is the standardized mechanism in the HTTP protocol that defines how responses can be stored and reused to improve web performance, reduce latency, and decrease network load.
-
B.
Cache
Cache is a Symfony component that provides a flexible, high-performance caching system for optimizing application performance and reducing redundant computations or data fetching.
-
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 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 7234
chosen
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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. |
Created at: March 30, 2026, 6:13 p.m.