Triple
T5768331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intelligent Tracking Prevention |
E127266
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tracking prevention feature |
C10339
|
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: tracking prevention feature Context triple: [Intelligent Tracking Prevention, instanceOf, tracking prevention feature]
-
A.
web browser privacy feature
chosen
A web browser privacy feature is a tool or setting that limits tracking, data collection, and exposure of user information while browsing the internet.
-
B.
track
A track is a defined path or course, often made of specific materials or markings, designed to guide or support the movement of objects, vehicles, or participants in activities such as transportation, racing, or recording.
-
C.
mobile device tracking service
A mobile device tracking service is a system that continuously monitors, records, and reports the real-time or historical locations and movement patterns of mobile devices for purposes such as security, analytics, and asset management.
-
D.
continuity feature
A continuity feature is a design element or mechanism that ensures a seamless, consistent experience or behavior across different states, times, or contexts within a system.
-
E.
park feature
A park feature is any designed or natural element within a park—such as paths, benches, playgrounds, gardens, or water bodies—that contributes to its use, aesthetics, or ecological value.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:49 p.m.