Triple
T10329114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IANA media type registry |
E242832
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Content-Type HTTP header |
E242831
|
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: Content-Type HTTP header | Statement: [IANA media type registry, relatedTo, Content-Type HTTP header]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Content-Type HTTP header Context triple: [IANA media type registry, relatedTo, Content-Type HTTP header]
-
A.
HTTP Content-Type header
chosen
The HTTP Content-Type header is a response header that tells clients the media type and character encoding of the returned content so they can interpret it correctly.
-
B.
Location HTTP header
The Location HTTP header is a response header used by web servers to indicate the URL to which a client should be redirected or where a newly created resource can be found.
-
C.
Transfer-Encoding header field
The Transfer-Encoding header field is an HTTP/1.1 mechanism that specifies how a message body is encoded for safe and efficient transfer between client and server, such as using chunked encoding.
-
D.
Accept-Charset
Accept-Charset is an HTTP request header that tells the server which character encodings the client is able to understand and prefers.
-
E.
Content-Range header field
The Content-Range header field is an HTTP response header used to indicate the specific byte range of a resource being returned, typically in support of partial content delivery and resumable downloads.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cfd54c8190b6f88598339536d1 |
completed | April 7, 2026, 10:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d71db4a8dc81909adb2a044e74fd6b |
completed | April 9, 2026, 3:32 a.m. |
Created at: April 6, 2026, 11:52 a.m.