Triple
T17234390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrome security policies |
E418321
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | enterprise browser policy set |
C30684
|
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: enterprise browser policy set Context triple: [Chrome security policies, instanceOf, enterprise browser policy set]
-
A.
Google Chrome edition
Google Chrome edition is a conceptual class representing a specific variant or release configuration of the Google Chrome web browser, distinguished by features, platform, or distribution channel.
-
B.
web browser backend configuration
chosen
A web browser backend configuration defines the settings and parameters that control how the browser’s underlying engines (networking, rendering, storage, security, etc.) operate and interact with system resources and external services.
-
C.
ChromeOS feature
A ChromeOS feature is a distinct capability or tool integrated into the ChromeOS operating system that enhances user productivity, security, connectivity, or overall device functionality.
-
D.
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.
-
E.
web browser privacy feature
A web browser privacy feature is a tool or setting that limits tracking, data collection, and exposure of user information while browsing the internet.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:39 a.m.