Triple
T28613083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Live Toolbar |
E724214
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | browser add-on |
C7003
|
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 add-on Context triple: [Windows Live Toolbar, instanceOf, browser add-on]
-
A.
browser plugin
chosen
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.
-
B.
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.
-
C.
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.
-
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.
browser extension manifest specification
A browser extension manifest specification is a structured configuration document that defines an extension’s metadata, permissions, resources, and behavior so browsers can correctly load, manage, and enforce its capabilities.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:30 a.m.