Triple
T380427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WHATWG |
E8665
|
entity |
| Predicate | develops |
P73
|
FINISHED |
| Object |
MIME Sniffing Standard
The MIME Sniffing Standard is a web specification that defines how browsers should determine the media type of resources to improve interoperability and security on the web.
|
E48503
|
NE FINISHED |
How this triple was built (4 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: MIME Sniffing Standard | Statement: [WHATWG, develops, MIME Sniffing Standard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MIME Sniffing Standard Context triple: [WHATWG, develops, MIME Sniffing Standard]
-
A.
RFC 6176 (prohibition of SSL 2.0)
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally deprecates and forbids the use of the insecure SSL 2.0 protocol in favor of more secure TLS versions.
-
B.
RFC 7232
RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
-
C.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
D.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
E.
RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: MIME Sniffing Standard Triple: [WHATWG, develops, MIME Sniffing Standard]
Generated description
The MIME Sniffing Standard is a web specification that defines how browsers should determine the media type of resources to improve interoperability and security on the web.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: MIME Sniffing Standard Target entity description: The MIME Sniffing Standard is a web specification that defines how browsers should determine the media type of resources to improve interoperability and security on the web.
-
A.
RFC 6176 (prohibition of SSL 2.0)
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally deprecates and forbids the use of the insecure SSL 2.0 protocol in favor of more secure TLS versions.
-
B.
RFC 7232
RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
-
C.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
D.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
E.
RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
- F. None of above. chosen
Provenance (5 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2c95088190a603bb1ee076ebd6 |
completed | Feb. 28, 2026, 1:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3faffa5848190b77503516f3d0ba6 |
completed | March 1, 2026, 8:38 a.m. |
| NEDg | Description generation | batch_69a3fb912d9881909d8eb02cdae70163 |
completed | March 1, 2026, 8:40 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69a3fd99e73c8190b5a92856ca0a4b82 |
completed | March 1, 2026, 8:49 a.m. |
Created at: Feb. 28, 2026, 1:08 p.m.