Triple
T30300725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motion Photos |
E770644
|
entity |
| Predicate | savesPrimaryFrameAs |
P74584
|
FINISHED |
| Object | high-resolution still image |
—
|
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: high-resolution still image | Statement: [Motion Photos, savesPrimaryFrameAs, high-resolution still image]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: savesPrimaryFrameAs Context triple: [Motion Photos, savesPrimaryFrameAs, high-resolution still image]
-
A.
canBeSavedAs
chosen
Indicates that one entity is capable of being stored or preserved in the form or format of another entity.
-
B.
primaryFile
Indicates that one file in a set is designated as the main or most important file associated with a given entity or context.
-
C.
sawAsPrimary
Indicates that one entity regarded another entity as the main or most important option, focus, or choice among alternatives.
-
D.
supportsSavingToCameraRoll
Indicates whether an action or feature allows content to be saved directly to the device’s camera roll.
-
E.
framesAs
Indicates how one entity presents, characterizes, or interprets another entity or situation in a particular light or context.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6813a47dc81908cc75bae4d2b97cc |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:48 p.m.