Triple
T10329419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Permissions API specification |
E242838
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Browser API specification |
C18777
|
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: Browser API specification Context triple: [Permissions API specification, instanceOf, Browser API specification]
-
A.
browser API
chosen
A browser API is a set of standardized interfaces provided by a web browser that allow web pages and applications to interact with browser features, the underlying device, and external resources in a controlled way.
-
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 specification
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.
-
D.
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.
-
E.
platform specification
A platform specification is a detailed description of the hardware, software, interfaces, and constraints that define the environment on which a system or application is designed to operate.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:52 a.m.