Triple
T20003347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple M8 motion coprocessor |
E494389
|
entity |
| Predicate | tracksSensor |
P138308
|
FINISHED |
| Object | accelerometer |
—
|
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: accelerometer | Statement: [Apple M8 motion coprocessor, tracksSensor, accelerometer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tracksSensor Context triple: [Apple M8 motion coprocessor, tracksSensor, accelerometer]
-
A.
trackSystem
Indicates a relationship where one entity monitors, records, or follows the status, behavior, or changes of another entity within a system.
-
B.
trackingAvailable
Indicates that tracking information or functionality is available for the associated item, process, or interaction.
-
C.
trackGauge
Indicates the distance between the inner faces of the rails in a railway track system.
-
D.
tracksLocation
Indicates that one entity monitors and records the geographic position or movement of another entity over time.
-
E.
trackAccess
Indicates that one entity monitors, records, or keeps a log of another entity’s access or usage of a resource.
- F. None of above. chosen
Provenance (4 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a3ad148190918f9dce755fe470 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:33 p.m.