Triple
T30300705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motion Photos |
E770644
|
entity |
| Predicate | playbackSupportedIn |
P50341
|
FINISHED |
| Object | Google Photos |
—
|
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: Google Photos | Statement: [Motion Photos, playbackSupportedIn, Google Photos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playbackSupportedIn Context triple: [Motion Photos, playbackSupportedIn, Google Photos]
-
A.
playableWith
chosen
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
B.
supportsVideoPlayback
Indicates that an entity is capable of playing or rendering video content.
-
C.
playbackMethod
Indicates the manner or technique by which media content is played back or rendered.
-
D.
playbackCharacteristic
Indicates the specific way in which something is played back, such as its playback behavior, quality, or technical properties during reproduction.
-
E.
playbackAccess
Indicates that one entity is permitted to play back or view media content controlled or owned by another entity.
- 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.