Triple
T33316251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Health Research |
E853023
|
entity |
| Predicate | participantDevice |
P99560
|
FINISHED |
| Object | consumer smartphones |
—
|
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: consumer smartphones | Statement: [Apple Health Research, participantDevice, consumer smartphones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantDevice Context triple: [Apple Health Research, participantDevice, consumer smartphones]
-
A.
testedDevice
Indicates that one entity has performed a test on, or experimentally evaluated, another entity as a device.
-
B.
targetedDevice
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
-
C.
characteristicDevice
chosen
Indicates that a device is a defining or typical instrument, tool, or equipment associated with a particular entity, context, or activity.
-
D.
relatedDevice
Indicates that one device has an association or connection to another device, without specifying the exact nature of that relationship.
-
E.
testedDeviceType
Indicates that one entity is the type or category of device on which another entity has been tested.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:33 a.m.