Triple
T30909267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feels Like Home |
E787394
|
entity |
| Predicate | performedInVocalStyle |
P108283
|
FINISHED |
| Object | ballad singing |
—
|
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: ballad singing | Statement: [Feels Like Home, performedInVocalStyle, ballad singing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedInVocalStyle Context triple: [Feels Like Home, performedInVocalStyle, ballad singing]
-
A.
artisticVocalStyle
chosen
Indicates a relationship where an entity’s vocal performance is characterized by a particular artistic style or expressive manner of singing or speaking.
-
B.
hasVocalStyleComparedTo
Indicates a comparison between entities based on the similarity or resemblance of their vocal style.
-
C.
introducedVocalStyleOf
Indicates that one entity initiated or brought into use the vocal style characteristic of another entity.
-
D.
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.
-
E.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: April 29, 2026, 8:50 p.m.