Triple
T9004580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live Photos |
E215111
|
entity |
| Predicate | toggleInCameraUI |
P85680
|
FINISHED |
| Object | Live Photo button |
—
|
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: Live Photo button | Statement: [Live Photos, toggleInCameraUI, Live Photo button]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toggleInCameraUI Context triple: [Live Photos, toggleInCameraUI, Live Photo button]
-
A.
supportsCameraControl
Indicates that one entity provides functionality for another entity to remotely manage or adjust camera settings or operations.
-
B.
usesCameraType
Indicates that one entity employs or operates a specific type or category of camera.
-
C.
meetsInCamera
Indicates that two or more entities are physically present together in the same camera frame or shot at the same time.
-
D.
hasCamera
Indicates that an entity is equipped with or possesses a camera.
-
E.
hasDedicatedCameraButton
Indicates that an object or device includes a specific physical button intended solely for activating or controlling the camera function.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6959497c8190a748c78504dd2eb6 |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:05 p.m.