Triple
T36911968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bach’s chorale harmonizations |
E912931
|
entity |
| Predicate | typicalCadences |
P205632
|
FINISHED |
| Object | perfect authentic cadence |
—
|
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: perfect authentic cadence | Statement: [Bach’s chorale harmonizations, typicalCadences, perfect authentic cadence]
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 (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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.