Triple
T23709423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitbit privacy policy |
E585817
|
entity |
| Predicate | coversDataType |
P33715
|
FINISHED |
| Object | account information |
—
|
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: account information | Statement: [Fitbit privacy policy, coversDataType, account information]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversDataType Context triple: [Fitbit privacy policy, coversDataType, account information]
-
A.
dataTypes
chosen
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
B.
appliesToDataType
Indicates that a rule, operation, or construct is specifically intended to be used with, or is valid for, a particular data type.
-
C.
analyzesDataType
Indicates that one entity examines, interprets, or evaluates a particular type or category of data.
-
D.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
E.
containsDataAbout
Indicates that one entity holds or includes information or records pertaining to another entity.
- 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.