Triple
T30300596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPhone 6s |
E770642
|
entity |
| Predicate | motionCoprocessor |
P169060
|
FINISHED |
| Object | Apple M9 |
—
|
NE NERFINISHED |
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: Apple M9 | Statement: [iPhone 6s, motionCoprocessor, Apple M9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motionCoprocessor Context triple: [iPhone 6s, motionCoprocessor, Apple M9]
-
A.
wearerDevice
Indicates that a device is worn or carried by a particular entity (the wearer).
-
B.
sensorBand
Indicates that an entity is associated with or operates within a specific sensor frequency band or range.
-
C.
hasProximitySensor
Indicates that an entity is equipped with a sensor capable of detecting nearby objects or measuring its distance to them.
-
D.
wearableBy
Indicates that one entity is designed or suitable to be worn on the body by another entity.
-
E.
characteristicDevice
Indicates that a device is a defining or typical instrument, tool, or equipment associated with a particular entity, context, or activity.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6813a47dc81908cc75bae4d2b97cc |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 29, 2026, 7:48 p.m.