Triple
T22159189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peterloo Overture |
E547622
|
entity |
| Predicate | tonalStyle |
P67730
|
FINISHED |
| Object | tonal |
—
|
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: tonal | Statement: [Peterloo Overture, tonalStyle, tonal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tonalStyle Context triple: [Peterloo Overture, tonalStyle, tonal]
-
A.
tonalDesign
Indicates the relationship in which one entity defines, specifies, or embodies the tonal structure or tonal scheme used by another entity (such as a work, passage, or system).
-
B.
tonal
chosen
Indicates that one entity has a tone, pitch pattern, or tonal quality in relation to another (such as a language, sound, or musical element).
-
C.
inTonality
Indicates that something (such as a musical element, passage, or piece) is expressed, structured, or interpreted within a specific musical key or tonal framework.
-
D.
tonalCharacteristic
Indicates the specific quality or character of a sound’s tone, such as its color, texture, or expressive nuance, in relation to an entity.
-
E.
tonalCenter
Indicates that one musical element functions as the primary pitch or key center around which another musical element is organized.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a2b5b10819090630fbadacb67af |
completed | April 28, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.