Triple
T36911968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bach’s chorale harmonizations |
E912931
|
entity |
| Predicate | typicalCadences |
—
|
GENERATED |
| Object | perfect authentic cadence |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCadences Context triple: [Bach’s chorale harmonizations, typicalCadences, perfect authentic cadence]
-
A.
typicalCadenzasBy
Indicates that a particular cadenza is characteristically or commonly composed or used by a given musician or composer.
-
B.
typicalChord
Indicates that a chord is a standard, commonly occurring, or characteristic instance within a given musical or harmonic context.
-
C.
typicalIChord
Indicates that a chord is a standard or characteristic instance of the I (tonic) chord within a given musical context.
-
D.
tonalityProgression
Indicates a change or development in musical key or tonal center over the course of a piece or passage.
-
E.
typicalIVChord
Indicates that a chord functions as a standard or commonly used IV (subdominant) chord within a given harmonic context.
- F. None of above. chosen
Provenance (1 batch)
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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.