Triple
T8625731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breathless |
E204275
|
entity |
| Predicate | cinematicTechniqueUsed |
P2760
|
FINISHED |
| Object | jump cuts |
—
|
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: jump cuts | Statement: [Breathless, cinematicTechniqueUsed, jump cuts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cinematicTechniqueUsed Context triple: [Breathless, cinematicTechniqueUsed, jump cuts]
-
A.
filmingTechnique
chosen
Indicates the specific method or style used to capture visual content during the filming process.
-
B.
cinematographyBy
Indicates that the cinematographic work (such as the camera work or visual style of a film or video) is created or supervised by a specified person or entity.
-
C.
cinematicContext
Indicates the relationship in which something is situated within, shaped by, or relevant to the circumstances, style, or conventions of cinema or film.
-
D.
hasDramaticTechnique
Indicates that one entity employs, features, or is characterized by a particular dramatic technique associated with another entity.
-
E.
filmicFunction
Indicates the role or purpose that something serves within the structure, style, or narrative function of a film.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:26 p.m.