Triple
T30453320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Me Back to Life |
E774779
|
entity |
| Predicate | hasEmotionallyChargedVocals |
P115288
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Love Me Back to Life, hasEmotionallyChargedVocals, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmotionallyChargedVocals Context triple: [Love Me Back to Life, hasEmotionallyChargedVocals, true]
-
A.
hasEmotiveVocals
chosen
Indicates that the subject produces vocals characterized by strong or expressive emotion.
-
B.
hasAggressiveVocals
Indicates that the subject produces or features vocals delivered in an intense, harsh, or forceful manner.
-
C.
hasEnergeticVocals
Indicates that the subject performs vocals characterized by high energy, intensity, or liveliness.
-
D.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
E.
hasEuphoricVocals
Indicates that the subject features or produces vocals characterized by intense happiness, excitement, or uplifting emotional expression.
- 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_69f22494fb60819095d893de0284f886 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:09 p.m.