Triple
T33434637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encrypted Media Extensions |
E856212
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | HTML5-related specification |
C2123
|
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: HTML5-related specification Context triple: [Encrypted Media Extensions, instanceOf, HTML5-related specification]
-
A.
W3C specification
chosen
A W3C specification is an official, collaboratively developed technical standard published by the World Wide Web Consortium that defines interoperable protocols, formats, and best practices for the World Wide Web.
-
B.
WHATWG specification
A WHATWG specification is a living technical standard developed by the Web Hypertext Application Technology Working Group that defines and evolves core web platform technologies such as HTML, DOM, and related APIs.
-
C.
W3C technical specification
A W3C technical specification is a formal, consensus-based document published by the World Wide Web Consortium that defines standards, protocols, and guidelines to ensure the interoperability and evolution of the World Wide Web.
-
D.
HTML specification proposal
A HTML specification proposal is a formal document outlining suggested changes, additions, or clarifications to the HTML standard, including rationale, technical details, and potential impacts on existing implementations.
-
E.
web standards documentation
Web standards documentation is the authoritative, structured reference that defines and explains the specifications, best practices, and implementation details for technologies used on the World Wide Web.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.