Triple
T30300724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motion Photos |
E770644
|
entity |
| Predicate | capturesAudio |
P48651
|
FINISHED |
| Object | yes, when supported |
—
|
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: yes, when supported | Statement: [Motion Photos, capturesAudio, yes, when supported]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturesAudio Context triple: [Motion Photos, capturesAudio, yes, when supported]
-
A.
usesAudioFrom
Indicates that one entity incorporates or relies on the audio content produced or provided by another entity.
-
B.
hasAudioFeature
chosen
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
C.
containsSound
Indicates that one entity includes, embodies, or produces the sound associated with another entity.
-
D.
audioStreaming
Indicates that one entity is transmitting audio data in real time for another entity to receive or play back.
-
E.
soundRecordingBy
Indicates that a sound recording was created, performed, or produced by a particular agent (such as an artist, band, or producer).
- 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_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 7:48 p.m.