Triple
T30300703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motion Photos |
E770644
|
entity |
| Predicate | defaultFileFormat |
P85676
|
FINISHED |
| Object | JPEG with embedded video data |
—
|
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: JPEG with embedded video data | Statement: [Motion Photos, defaultFileFormat, JPEG with embedded video data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultFileFormat Context triple: [Motion Photos, defaultFileFormat, JPEG with embedded video data]
-
A.
defaultFileFormatVideo
chosen
Indicates the default file format used for saving or exporting video content.
-
B.
typicalFileFormat
Indicates the usual or standard file format typically associated with or used for a given entity or context.
-
C.
fileFormatOutput
Indicates the specific file format in which data, content, or results are produced or exported.
-
D.
defaultPackageFormat
Indicates the standard or primary packaging format that is used by default for an item or distribution.
-
E.
fileFormatStandard
Indicates that something conforms to, specifies, or defines a standardized structure and rules for how data is organized and stored in a file.
- 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_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 29, 2026, 7:48 p.m.