Triple
T10396165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orchestral Variations on a Theme from 'Che' |
E245026
|
entity |
| Predicate | hasMainThemeSource |
P60019
|
FINISHED |
| Object | theme from the film Che |
—
|
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: theme from the film Che | Statement: [Orchestral Variations on a Theme from 'Che', hasMainThemeSource, theme from the film Che]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainThemeSource Context triple: [Orchestral Variations on a Theme from 'Che', hasMainThemeSource, theme from the film Che]
-
A.
hasMainSource
chosen
Indicates that one entity serves as the primary or principal source or origin for another entity.
-
B.
hasMainImageSource
Indicates that an entity is associated with a primary image file or URL that serves as its main visual representation.
-
C.
hasThemeType
Indicates that something is associated with or characterized by a particular thematic category or type.
-
D.
hasCentralTheme
Indicates that one entity serves as the primary or dominant theme or subject matter of another entity.
-
E.
hasThemeConnection
Indicates a relationship where one entity is linked to another through a shared or related theme, topic, or conceptual focus.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9cf79348190975d6c1791e3b621 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:06 p.m.