Triple
T34184499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skylar Grey |
E876919
|
entity |
| Predicate | featuredVocalistOn |
P8086
|
FINISHED |
| Object | Coming Home |
E11073
|
NE 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: Coming Home | Statement: [Skylar Grey, featuredVocalistOn, Coming Home]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredVocalistOn Context triple: [Skylar Grey, featuredVocalistOn, Coming Home]
-
A.
featuresVocalist
chosen
Indicates that one entity (such as a song, track, or performance) includes another entity serving as a vocalist or featured singer.
-
B.
vocalistIn
Indicates that a person serves as a vocalist (singer) in a particular musical group, band, or ensemble.
-
C.
guestVocalistIsFrontmanOf
Indicates that the guest vocalist performing on a work is also the lead singer (frontman) of the referenced band or primary musical act.
-
D.
recordingArtistOfGuestVocalist
Indicates that an artist is the primary recording artist on a work that features another artist as a guest vocalist.
-
E.
introducedVocalist
Indicates that one entity caused a vocalist to be presented or brought to public attention, typically for the first time.
- F. None of above.
Provenance (4 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0309a4e4d481908a6070b40d507aae |
completed | May 12, 2026, 11:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36d5d7ff648190a62efef46923c960 |
completed | June 20, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_6a03091ac1008190bf50357364d4e9e4 |
completed | May 12, 2026, 11:03 a.m. |
Created at: May 1, 2026, 1:55 a.m.