Triple
T1892407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | visionOS |
E41899
|
entity |
| Predicate | includesFramework |
P1393
|
FINISHED |
| Object | Core Motion |
E114978
|
NE 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: Core Motion | Statement: [visionOS, includesFramework, Core Motion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Core Motion Context triple: [visionOS, includesFramework, Core Motion]
-
A.
CoreMotion
chosen
CoreMotion is an Apple framework that provides access to motion and fitness data from device sensors such as accelerometers and gyroscopes.
-
B.
HealthKit framework
HealthKit framework is an Apple software framework that enables apps to securely access, store, and share users’ health and fitness data on iOS devices.
-
C.
CoreBluetooth
CoreBluetooth is an Apple framework that enables apps to communicate with Bluetooth Low Energy (BLE) devices for tasks like data exchange and peripheral control.
-
D.
WatchKit
WatchKit is Apple’s framework that enables developers to build and manage user interfaces and interactions for apps running on Apple Watch.
-
E.
HomeKit framework
HomeKit framework is Apple's software framework that enables iOS apps and Siri to configure, communicate with, and control compatible smart home accessories.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb1480a6c81909fcf5cce4c42fed4 |
completed | March 7, 2026, 5:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69addf6aba788190bb30420375b5db7f |
completed | March 8, 2026, 8:43 p.m. |
Created at: March 4, 2026, 7:34 p.m.