Triple
T12206532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accept-Charset |
E290850
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | HTTP request header |
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 request header Context triple: [Accept-Charset, instanceOf, HTTP request header]
-
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.
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.
-
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.
entity header field
An entity header field is a metadata component in a message (such as HTTP) that describes characteristics of the message body, including its content type, length, encoding, and other entity-specific information.
-
E.
general header field
A general header field is a reusable metadata field in a message or protocol header that applies to the overall message rather than to a specific component or payload.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:51 p.m.