Triple
T2703278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2068 |
E59281
|
entity |
| Predicate | definesHeaderField |
P3703
|
FINISHED |
| Object | Content-Type |
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 | Statement: [RFC 2068, definesHeaderField, Content-Type]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Content-Type Context triple: [RFC 2068, definesHeaderField, Content-Type]
-
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.
Content-Encoding
Content-Encoding is an HTTP header that specifies the compression or transformation applied to the body of a message so that recipients know how to decode it.
-
C.
MIME
MIME (Multipurpose Internet Mail Extensions) is an internet standard that extends the format of email to support text in character sets beyond ASCII, as well as attachments like images, audio, video, and application files.
-
D.
Accept-Encoding
Accept-Encoding is an HTTP request header that tells the server which content-encoding algorithms (like gzip or deflate) the client can handle so the server can choose an appropriate compression method.
-
E.
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.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda5011bc8190ae4e41da391e759c |
completed | March 7, 2026, 7:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afaf76caec8190930ead7931f7ea91 |
completed | March 10, 2026, 5:43 a.m. |
Created at: March 6, 2026, 9:55 p.m.