Triple
T23559920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In a Mellow Tone |
E579204
|
entity |
| Predicate | hasChordProgressionType |
P152792
|
FINISHED |
| Object | contrafact |
—
|
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: contrafact | Statement: [In a Mellow Tone, hasChordProgressionType, contrafact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChordProgressionType Context triple: [In a Mellow Tone, hasChordProgressionType, contrafact]
-
A.
usesChordChangesOf
Indicates that one musical work employs the same or substantially similar chord progression as another work.
-
B.
tonalityProgression
Indicates a change or development in musical key or tonal center over the course of a piece or passage.
-
C.
typicalChord
Indicates that a chord is a standard, commonly occurring, or characteristic instance within a given musical or harmonic context.
-
D.
typicalIChord
Indicates that a chord is a standard or characteristic instance of the I (tonic) chord within a given musical context.
-
E.
isChromatic
Indicates that something exhibits chromatic properties, such as involving or characterized by multiple colors or tones.
- F. None of above. chosen
Provenance (4 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af672db4819087dbff2c0dfadd7f |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:12 p.m.