Triple
T5016949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Health app |
E112758
|
entity |
| Predicate | storesDataFrom |
P1596
|
FINISHED |
| Object | iPhone motion sensors |
—
|
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: iPhone motion sensors | Statement: [Health app, storesDataFrom, iPhone motion sensors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesDataFrom Context triple: [Health app, storesDataFrom, iPhone motion sensors]
-
A.
storesDataType
Indicates that an entity is designed to hold, manage, or persist information of a specified data type.
-
B.
dataStorage
chosen
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
C.
storesConfigurationFor
Indicates that one entity holds or maintains configuration settings that are used by or apply to another entity.
-
D.
storesObjectsAs
Indicates that one entity keeps or maintains other entities within it as stored items or contents.
-
E.
storesIndexesIn
Indicates that one entity maintains and holds index data within another storage entity or system.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd734037a88190a950db814412a023 |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.