Triple
T32541886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows privacy dashboard |
E831733
|
entity |
| Predicate | userControlScope |
P42519
|
FINISHED |
| Object | Microsoft account–linked data |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Microsoft account–linked data | Statement: [Windows privacy dashboard, userControlScope, Microsoft account–linked data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userControlScope Context triple: [Windows privacy dashboard, userControlScope, Microsoft account–linked data]
-
A.
commonsControl
Indicates that one entity has authority or regulatory power over shared or common resources involving another entity.
-
B.
utilitiesControlledBy
Indicates that one entity has authority over, management of, or operational control of another entity’s utilities or utility services.
-
C.
scopeOfControl
Indicates the extent or range within which an entity has authority, influence, or control over another entity or set of entities.
-
D.
controlsAccessTo
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
-
E.
accessScope
chosen
Indicates the extent or boundaries of access that one entity has to another entity or resource.
- F. None of above.
Provenance (3 batches)
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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c57f14348190a0e2b98597e5ba25 |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.