Triple
T16901759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F major |
E424453
|
entity |
| Predicate | subdominantTriad |
P100469
|
FINISHED |
| Object | B♭–D–F |
—
|
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: B♭–D–F | Statement: [F major, subdominantTriad, B♭–D–F]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdominantTriad Context triple: [F major, subdominantTriad, B♭–D–F]
-
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.
notableTriad
Indicates a three-way association among entities that is particularly significant, prominent, or noteworthy compared to other possible groupings.
-
C.
secondaryTone
Indicates that one tone functions as a secondary or supporting tonal element in relation to a primary tone within a given context.
-
D.
secondaryConstituent
Indicates that one entity functions as a secondary or subordinate component, element, or member within the structure or composition of another entity.
-
E.
diatonicScale
chosen
Indicates that a musical element (such as a note, chord, or melody) belongs to or is derived from a specific diatonic scale.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8dc7cf08190ad935935d8daf1d0 |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.