Triple
T17380954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sublime |
E422564
|
entity |
| Predicate | frontmanCauseOfDeath |
P127272
|
FINISHED |
| Object | heroin overdose |
—
|
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: heroin overdose | Statement: [Sublime, frontmanCauseOfDeath, heroin overdose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontmanCauseOfDeath Context triple: [Sublime, frontmanCauseOfDeath, heroin overdose]
-
A.
isFrontmanOf
Indicates that a person serves as the lead singer or primary representative performer of a band or musical group.
-
B.
frontmanStageName
Indicates that the specified stage name is used by the person who serves as the frontman (lead performer) of a musical group or band.
-
C.
founderDiedIn
Indicates that the person who founded an entity died in a specified place or at a specified time.
-
D.
guestVocalistIsFrontmanOf
Indicates that the guest vocalist performing on a work is also the lead singer (frontman) of the referenced band or primary musical act.
-
E.
notableBandMember
Indicates that the subject is a member of the band in the object and is recognized as particularly prominent or significant within that band.
- F. None of above. chosen
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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a860f588190915e0671f44bfbcc |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:45 a.m.