Triple
T10558267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orchestral Variations on a Theme from 'Pain and Glory' |
E249145
|
entity |
| Predicate | derivesThemeFromWorkType |
P83682
|
FINISHED |
| Object | film |
—
|
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: film | Statement: [Orchestral Variations on a Theme from 'Pain and Glory', derivesThemeFromWorkType, film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivesThemeFromWorkType Context triple: [Orchestral Variations on a Theme from 'Pain and Glory', derivesThemeFromWorkType, film]
-
A.
associatedWithWorkTheme
Indicates a relationship where something is connected or related to a particular work theme or subject matter.
-
B.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
C.
usesThemeFrom
chosen
Indicates that one work incorporates, references, or is based on the thematic material of another work.
-
D.
originallyFromWorkType
Indicates that one entity was derived, adapted, or sourced from an original work of a specified type (e.g., book, film, artwork).
-
E.
workFromWhichTitleDerived
Indicates that a title is derived from, or based on, a particular underlying work.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5271521a4819086d96e1f183ab07a |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:35 p.m.