Triple
T28085666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lovesick Blues |
E709814
|
entity |
| Predicate | hasVocalStyleFeature |
P156193
|
FINISHED |
| Object | yodeling |
—
|
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: yodeling | Statement: [Lovesick Blues, hasVocalStyleFeature, yodeling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVocalStyleFeature Context triple: [Lovesick Blues, hasVocalStyleFeature, yodeling]
-
A.
hasHookVocalStyle
Indicates that an entity (typically a musical work or performance) features a distinctive, catchy vocal delivery or refrain intended to serve as a memorable hook.
-
B.
hasVocalStyleComparedTo
Indicates a comparison between entities based on the similarity or resemblance of their vocal style.
-
C.
hasVocalCharacter
chosen
Indicates that an entity possesses a particular vocal quality, style, or characteristic in its sound or voice.
-
D.
hasSecondaryVocalStyle
Indicates that an entity (typically a performer or recording) employs an additional, non-primary vocal style alongside its main vocal style.
-
E.
hasVocalForces
Indicates that an entity involves or employs vocal performers or vocal parts as a contributing force.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 8:55 p.m.