Triple
T30300704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motion Photos |
E770644
|
entity |
| Predicate | storesVideoAs |
P169388
|
FINISHED |
| Object | embedded MP4 segment |
—
|
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: embedded MP4 segment | Statement: [Motion Photos, storesVideoAs, embedded MP4 segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesVideoAs Context triple: [Motion Photos, storesVideoAs, embedded MP4 segment]
-
A.
homeVideo
Indicates that an entity is a video recording made in a domestic or personal setting, typically by non-professionals for private use.
-
B.
musicVideoLocation
Indicates the place or setting where a music video is filmed or takes place.
-
C.
homeVideoSuccess
Indicates that a film or video release achieved notable success in the home video market (e.g., VHS, DVD, Blu-ray, or digital home distribution).
-
D.
associatedVideoImagery
Indicates a relationship where specific video imagery is linked or connected to another entity (such as an event, object, or record) as related visual content.
-
E.
homeVideoReleaseOfWork
Indicates that one work is the home video release (e.g., VHS, DVD, Blu-ray, digital home media) version of another work.
- 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_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_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:48 p.m.