Triple
T38599270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C major |
E934164
|
entity |
| Predicate | hasSupertonicChord |
P142445
|
FINISHED |
| Object | D minor |
—
|
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: D minor | Statement: [C major, hasSupertonicChord, D minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupertonicChord Context triple: [C major, hasSupertonicChord, D minor]
-
A.
supertonicKey
Indicates that one musical key stands in the supertonic (second scale degree) relationship to another key.
-
B.
supertonicTriad
chosen
Indicates that a triad chord functions as the supertonic (built on the second scale degree) within a given key or tonal context.
-
C.
usesChord
Indicates that one entity employs or incorporates a particular chord in its structure, performance, or composition.
-
D.
containsTetrachord
Indicates that one musical structure includes a specific tetrachord as a contiguous subset of its pitches.
-
E.
usesChordChangesOf
Indicates that one musical work employs the same or substantially similar chord progression as another work.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a009a0e1fa481909ed881012009b268 |
completed | May 10, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_6a0092e9fcb08190a966d720684f25ec |
completed | May 10, 2026, 2:15 p.m. |
Created at: May 3, 2026, 4:32 p.m.