Triple
T22814271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manifest V2 |
E565060
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | browser extension manifest specification |
C46874
|
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 extension manifest specification Context triple: [Manifest V2, instanceOf, browser extension manifest specification]
-
A.
browser extension framework
A browser extension framework is a structured set of APIs, tools, and conventions that simplifies building, integrating, and managing extensions across one or more web browsers.
-
B.
browser extension catalog
A browser extension catalog is a curated collection or marketplace that organizes, describes, and distributes browser add-ons, enabling users to discover, compare, and install extensions that enhance their web browsing experience.
-
C.
browser plugin
A browser plugin is a small software component that adds specific features or functionality to a web browser, enhancing or extending its capabilities beyond the default behavior.
-
D.
web browser feature experimentation system
A web browser feature experimentation system is a framework that enables controlled rollout, A/B testing, and data-driven evaluation of browser features across user segments to optimize performance, usability, and stability.
-
E.
HTTP extension
An HTTP extension is an addition to the core HTTP protocol that introduces new headers, methods, or behaviors to support extra functionality while remaining compatible with existing HTTP infrastructure.
- F. None of above. chosen
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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:33 p.m.