Triple
T23709417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitbit privacy policy |
E585817
|
entity |
| Predicate | describesProcessingOf |
P64843
|
FINISHED |
| Object | 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: personal data | Statement: [Fitbit privacy policy, describesProcessingOf, personal data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesProcessingOf Context triple: [Fitbit privacy policy, describesProcessingOf, personal data]
-
A.
documentedProcess
chosen
Indicates that a process has been formally recorded, described, or specified in documentation.
-
B.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
C.
typicalProcess
Indicates that the related process is characteristic, usual, or commonly occurring for the given entity or context.
-
D.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
E.
broaderProcess
Indicates that one process encompasses, includes, or provides the larger context for another, more specific process.
- 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.