Triple
T28275379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon in D |
E712973
|
entity |
| Predicate | chordProgression |
P152792
|
FINISHED |
| Object | I–V–vi–iii–IV–I–IV–V in D major |
—
|
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: I–V–vi–iii–IV–I–IV–V in D major | Statement: [Canon in D, chordProgression, I–V–vi–iii–IV–I–IV–V in D major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chordProgression Context triple: [Canon in D, chordProgression, I–V–vi–iii–IV–I–IV–V in D major]
-
A.
tonalityProgression
Indicates a change or development in musical key or tonal center over the course of a piece or passage.
-
B.
hasChordProgressionType
chosen
Indicates that a musical piece, section, or passage exhibits a specific type or pattern of chord progression.
-
C.
typicalChord
Indicates that a chord is a standard, commonly occurring, or characteristic instance within a given musical or harmonic context.
-
D.
usesChordChangesOf
Indicates that one musical work employs the same or substantially similar chord progression as another work.
-
E.
typicalIChord
Indicates that a chord is a standard or characteristic instance of the I (tonic) chord within a given musical 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6444b5f288190b5c6ed6340b83427 |
completed | May 2, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:20 p.m.