Triple
T33436014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP cookie |
E856240
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | HTTP header-based mechanism |
C24497
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: HTTP header-based mechanism Context triple: [HTTP cookie, instanceOf, HTTP header-based mechanism]
-
A.
HTTP header field
chosen
An HTTP header field is a key-value pair in an HTTP message that conveys metadata and control information between a client and server, such as content type, caching policies, and authentication details.
-
B.
protocol header field
A protocol header field is a structured piece of metadata within a network protocol header that conveys control, addressing, or formatting information needed to correctly interpret and route the associated data.
-
C.
HTTP extension
An HTTP extension is an addition to the core HTTP protocol that introduces new headers, methods, or behaviors to support extra functionality while remaining compatible with existing HTTP infrastructure.
-
D.
networking mechanism
A networking mechanism is a conceptual component or process that enables, manages, or optimizes the exchange of data between devices or systems within a network.
-
E.
response header field
A response header field is a name-value pair in an HTTP response that conveys metadata about the response or the server’s handling of the request.
- F. None of above.
Provenance (1 batch)
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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.