Triple
T33334104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jitterbug Waltz |
E853486
|
entity |
| Predicate | hasMelodicContour |
P63178
|
FINISHED |
| Object | stepwise motion with leaps |
—
|
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: stepwise motion with leaps | Statement: [Jitterbug Waltz, hasMelodicContour, stepwise motion with leaps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMelodicContour Context triple: [Jitterbug Waltz, hasMelodicContour, stepwise motion with leaps]
-
A.
melodicContour
chosen
Indicates the pattern of pitch movement over time in a musical line, describing how notes rise, fall, or stay level relative to one another.
-
B.
hasMelodicRange
Indicates that a musical piece, phrase, or part spans a specific interval between its lowest and highest pitches.
-
C.
hasSimpleMelodicProfile
Indicates that the subject’s melody is uncomplicated, using limited pitch variation and straightforward, easily recognizable melodic patterns.
-
D.
hasMelodicHook
Indicates that a musical piece contains a distinctive, memorable melodic phrase designed to catch the listener’s attention.
-
E.
hasMelody
Indicates that one entity possesses, contains, or is characterized by a particular melody.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: May 1, 2026, 1:34 a.m.