Triple
T27818685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orange Blossom Special |
E702751
|
entity |
| Predicate | hasMelodicElement |
P112460
|
FINISHED |
| Object | whistle imitations |
—
|
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: whistle imitations | Statement: [Orange Blossom Special, hasMelodicElement, whistle imitations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMelodicElement Context triple: [Orange Blossom Special, hasMelodicElement, whistle imitations]
-
A.
hasMelody
Indicates that one entity possesses, contains, or is characterized by a particular melody.
-
B.
hasMelodyInstrument
Indicates that something uses or features a particular instrument to carry the main melody.
-
C.
hasMelodicHook
chosen
Indicates that a musical piece contains a distinctive, memorable melodic phrase designed to catch the listener’s attention.
-
D.
isMelodic
Indicates that something possesses a tuneful, harmonious, or musically pleasing quality.
-
E.
hasMelodicRange
Indicates that a musical piece, phrase, or part spans a specific interval between its lowest and highest pitches.
- 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 27, 2026, 5:47 p.m.