Triple
T21854344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweet Lorraine |
E539583
|
entity |
| Predicate | hasChordProgressionCharacteristic |
P40268
|
FINISHED |
| Object | functional harmony |
—
|
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: functional harmony | Statement: [Sweet Lorraine, hasChordProgressionCharacteristic, functional harmony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChordProgressionCharacteristic Context triple: [Sweet Lorraine, hasChordProgressionCharacteristic, functional harmony]
-
A.
usesChordChangesOf
Indicates that one musical work employs the same or substantially similar chord progression as another work.
-
B.
tonalityProgression
chosen
Indicates a change or development in musical key or tonal center over the course of a piece or passage.
-
C.
hasVerseChorusStructure
Indicates that something, typically a musical composition, is organized using a recurring pattern of verses and choruses.
-
D.
isChromatic
Indicates that something exhibits chromatic properties, such as involving or characterized by multiple colors or tones.
-
E.
usesChorale
Indicates that one entity incorporates or employs a chorale (a hymn-like musical piece) within its structure or content.
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0bd5ba9288190af962117124f6483 |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.