Triple
T27613549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPhone (remote control) |
E700380
|
entity |
| Predicate | deviceTypeControlled |
P48650
|
FINISHED |
| Object | Mac |
—
|
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: Mac | Statement: [iPhone (remote control), deviceTypeControlled, Mac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deviceTypeControlled Context triple: [iPhone (remote control), deviceTypeControlled, Mac]
-
A.
controlsDeviceType
chosen
Indicates that an entity has authority over or can operate a specific type or category of device.
-
B.
testedDeviceType
Indicates that one entity is the type or category of device on which another entity has been tested.
-
C.
targetedDevice
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
-
D.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
E.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f630d5c31081909d20e8165cc0515f |
completed | May 2, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:12 p.m.