Triple
T27065902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autograph |
E685172
|
entity |
| Predicate | hasMetaCinematicElements |
P155555
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Autograph, hasMetaCinematicElements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMetaCinematicElements Context triple: [Autograph, hasMetaCinematicElements, true]
-
A.
hasCinematicFeature
Indicates that something possesses a specific cinematic characteristic, quality, or element related to film or visual storytelling.
-
B.
metacinematicElement
chosen
Indicates that one element in a work refers to, comments on, or foregrounds the nature, techniques, or conventions of cinema or filmmaking itself.
-
C.
hasCinematicThemes
Indicates that something incorporates or is characterized by themes, motifs, or stylistic elements commonly associated with cinema or film.
-
D.
hasCinematicShort
Indicates that an entity is associated with or includes a cinematic short film or short-form cinematic content.
-
E.
hasCutscenes
Indicates that the subject includes or features one or more non-interactive cinematic sequences (cutscenes).
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 27, 2026, 8:25 a.m.