Triple
T21004606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E minor |
E517381
|
entity |
| Predicate | leadingToneTriad |
P142446
|
FINISHED |
| Object | D–F♯–A |
—
|
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: D–F♯–A | Statement: [E minor, leadingToneTriad, D–F♯–A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadingToneTriad Context triple: [E minor, leadingToneTriad, D–F♯–A]
-
A.
dominantTriad
Indicates that one entity forms the primary or controlling component within a three-part (triadic) relationship involving the other two entities.
-
B.
leadingTone
Indicates that one musical pitch functions as a leading tone, creating a strong tendency to resolve stepwise (typically upward) to a specific target pitch.
-
C.
notableTriad
Indicates a three-way association among entities that is particularly significant, prominent, or noteworthy compared to other possible groupings.
-
D.
tonalityProgression
Indicates a change or development in musical key or tonal center over the course of a piece or passage.
-
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. chosen
Provenance (4 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc3b25ec8190aa4530d1f0bb2b9e |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:52 p.m.