Triple
T31534527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spin, O My Spinner |
E804568
|
entity |
| Predicate | hasMelodicFunction |
P41587
|
FINISHED |
| Object | source melody for symphonic works |
—
|
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: source melody for symphonic works | Statement: [Spin, O My Spinner, hasMelodicFunction, source melody for symphonic works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMelodicFunction Context triple: [Spin, O My Spinner, hasMelodicFunction, source melody for symphonic works]
-
A.
isMelodic
Indicates that something possesses a tuneful, harmonious, or musically pleasing quality.
-
B.
hasMelody
Indicates that one entity possesses, contains, or is characterized by a particular melody.
-
C.
hasMelodicHook
Indicates that a musical piece contains a distinctive, memorable melodic phrase designed to catch the listener’s attention.
-
D.
hasMelodicRange
Indicates that a musical piece, phrase, or part spans a specific interval between its lowest and highest pitches.
-
E.
musicalFunction
chosen
Indicates the specific role or function an entity plays within a musical context, such as its harmonic, structural, or performative purpose in a piece or performance.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: April 30, 2026, 10:03 p.m.