Triple
T725976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Try Sleeping with a Broken Heart |
E14725
|
entity |
| Predicate | vocalRangeShowcase |
P1151
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Try Sleeping with a Broken Heart, vocalRangeShowcase, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalRangeShowcase Context triple: [Try Sleeping with a Broken Heart, vocalRangeShowcase, yes]
-
A.
vocalRange
chosen
Indicates the span of pitches or notes that an entity (such as a singer or instrument) is capable of producing.
-
B.
featuresVocalist
Indicates that one entity (such as a song, track, or performance) includes another entity serving as a vocalist or featured singer.
-
C.
vocalizationMethod
Indicates the manner or technique by which an entity produces a sound or vocal expression.
-
D.
repertoireIncludes
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
E.
voiceType
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f839608190878a60eb7a044ed9 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.