Triple
T23709448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitbit privacy policy |
E585817
|
entity |
| Predicate | grantsUserRight |
P93739
|
FINISHED |
| Object | access personal 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: access personal data | Statement: [Fitbit privacy policy, grantsUserRight, access personal data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantsUserRight Context triple: [Fitbit privacy policy, grantsUserRight, access personal data]
-
A.
grantsPrivileges
Indicates that one entity confers specific rights, permissions, or advantages to another entity.
-
B.
grantsAbility
Indicates that one entity endows another entity with a specific capability or power that it did not previously possess.
-
C.
grantUse
Indicates that one entity gives another entity permission or authorization to use something.
-
D.
grantedRightsType
Indicates the specific category or nature of rights that have been granted in a given permission or authorization relationship.
-
E.
grantsPermissionFor
chosen
Indicates that one entity authorizes or allows another entity to perform a specific action or access a particular 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b775a4288190bbee7bd4b5bbcd75 |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.