Triple
T37359434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adagio in D major |
E927538
|
entity |
| Predicate | primaryMelodicRole |
P140756
|
FINISHED |
| Object | clarinet |
—
|
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: clarinet | Statement: [Adagio in D major, primaryMelodicRole, clarinet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMelodicRole Context triple: [Adagio in D major, primaryMelodicRole, clarinet]
-
A.
dominantNote
Indicates that one note functions as the dominant (fifth scale degree) in relation to another note, typically resolving to it harmonically.
-
B.
primaryInstrumentRole
chosen
Indicates that an entity serves as the main or leading instrument in a given role, context, or performance.
-
C.
tonalRole
Indicates the functional role that a musical element (such as a note, chord, or key) plays within a tonal context or hierarchy.
-
D.
dominantTone
Indicates the primary or most prominent emotional or stylistic tone that characterizes something in relation to other possible tones.
-
E.
subdominantKey
Indicates the musical key that functions as the subdominant (built on the fourth scale degree) in relation to a given tonic key.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.