Triple
T22028363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPhone Cellular Calls |
E544021
|
entity |
| Predicate | settingName |
P139583
|
FINISHED |
| Object | Calls on Other Devices |
—
|
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: Calls on Other Devices | Statement: [iPhone Cellular Calls, settingName, Calls on Other Devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingName Context triple: [iPhone Cellular Calls, settingName, Calls on Other Devices]
-
A.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
B.
knownAsSettingFor
Indicates that something is recognized or regarded as the typical or notable setting or backdrop for something else.
-
C.
indicatedSetting
chosen
Indicates that one entity specifies, denotes, or points out a particular setting or configuration associated with another entity.
-
D.
settingControlled
Indicates that one entity regulates, adjusts, or determines the configuration or parameters of another entity.
-
E.
settingAfter
Indicates that one setting or configuration occurs or is applied after another in a sequence or order.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127cdf5c08190ac804664d6e56fe2 |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.