Triple
T11590249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E major (BWV 1006) |
E274860
|
entity |
| Predicate | enharmonicEquivalentKey |
P57346
|
FINISHED |
| Object | F♭ 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: F♭ major | Statement: [E major (BWV 1006), enharmonicEquivalentKey, F♭ major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enharmonicEquivalentKey Context triple: [E major (BWV 1006), enharmonicEquivalentKey, F♭ major]
-
A.
subdominantKey
Indicates the musical key that functions as the subdominant (built on the fourth scale degree) in relation to a given tonic key.
-
B.
tonalityProgression
Indicates a change or development in musical key or tonal center over the course of a piece or passage.
-
C.
musicTheoryContext
Indicates that one entity is interpreted or analyzed within the framework, rules, or concepts of music theory in relation to another entity or situation.
-
D.
tonalCenter
Indicates that one musical element functions as the primary pitch or key center around which another musical element is organized.
-
E.
hasAlternativeNotation
chosen
Indicates that an entity can be represented or written in a different, equivalent form or notation.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d894643ae48190837502b713f5b9c6 |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.