Triple
T22257417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B major |
E550127
|
entity |
| Predicate | typicalVChord |
P125131
|
FINISHED |
| Object | F-sharp major triad |
—
|
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-sharp major triad | Statement: [B major, typicalVChord, F-sharp major triad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVChord Context triple: [B major, typicalVChord, F-sharp major triad]
-
A.
dominantTriad
chosen
Indicates that one entity forms the primary or controlling component within a three-part (triadic) relationship involving the other two entities.
-
B.
typicalScaleDegreePattern
Indicates the usual or most common sequence of scale degrees that characterizes a particular melodic, harmonic, or stylistic pattern.
-
C.
tonalityProgression
Indicates a change or development in musical key or tonal center over the course of a piece or passage.
-
D.
usesChordChangesOf
Indicates that one musical work employs the same or substantially similar chord progression as another work.
-
E.
leadingToneTriad
Indicates a triad built on the leading tone (the seventh scale degree) that functions to resolve toward the tonic harmony.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138c3cf64819087e270a1f50e629e |
completed | April 28, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:39 p.m.