Triple
T10396175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orchestral Variations on a Theme from 'Che' |
E245026
|
entity |
| Predicate | hasMediumOfPerformance |
P46721
|
FINISHED |
| Object | orchestra |
—
|
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: orchestra | Statement: [Orchestral Variations on a Theme from 'Che', hasMediumOfPerformance, orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMediumOfPerformance Context triple: [Orchestral Variations on a Theme from 'Che', hasMediumOfPerformance, orchestra]
-
A.
notablePerformanceMedium
Indicates the medium (such as film, stage, or television) in which an entity delivered a notable or distinguished performance.
-
B.
firstPerformanceMedium
chosen
Indicates the medium or format (e.g., stage, radio, television) in which a work was first performed.
-
C.
hasAssociatedMedium
Indicates that one entity is linked to another entity that serves as its medium, format, or channel of expression or transmission.
-
D.
performsMedium
Indicates that an entity carries out or executes an action, role, or function using a specified medium or means.
-
E.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
- 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.