Triple
T10156721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transfer-Encoding header field |
E233793
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | message header field |
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: message header field Context triple: [Transfer-Encoding header field, instanceOf, message header field]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
message authentication code
A message authentication code (MAC) is a short piece of information generated from a message and a secret key that verifies both the message’s integrity and the authenticity of its sender.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 9:09 p.m.