Triple
T38599273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C major |
E934164
|
entity |
| Predicate | hasDominantChord |
P125131
|
FINISHED |
| Object | G 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: G major triad | Statement: [C major, hasDominantChord, G major triad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDominantChord Context triple: [C major, hasDominantChord, G major triad]
-
A.
dominantNote
Indicates that one note functions as the dominant (fifth scale degree) in relation to another note, typically resolving to it harmonically.
-
B.
dominantTone
Indicates the primary or most prominent emotional or stylistic tone that characterizes something in relation to other possible tones.
-
C.
dominantTriad
chosen
Indicates that one entity forms the primary or controlling component within a three-part (triadic) relationship involving the other two entities.
-
D.
subdominantKey
Indicates the musical key that functions as the subdominant (built on the fourth scale degree) in relation to a given tonic key.
-
E.
typicalChord
Indicates that a chord is a standard, commonly occurring, or characteristic instance within a given musical or harmonic context.
- 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_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:32 p.m.