Triple
T29780380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chuck Schuldiner |
E755497
|
entity |
| Predicate | notableAlbumWithDeath |
P31992
|
FINISHED |
| Object | Scream Bloody Gore |
E1256032
|
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: Scream Bloody Gore | Statement: [Chuck Schuldiner, notableAlbumWithDeath, Scream Bloody Gore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAlbumWithDeath Context triple: [Chuck Schuldiner, notableAlbumWithDeath, Scream Bloody Gore]
-
A.
notableDeath
Indicates that an entity’s death is considered significant or noteworthy in some context.
-
B.
notableAlbumContribution
Indicates that an entity made a significant creative or performance contribution to a particular music album.
-
C.
notableAlbumReleaseYear
Indicates the year in which a notable album associated with the subject was released.
-
D.
recordingArtistDeathBeforeRelease
Indicates that the recording artist died before the release of the recording or work in question.
-
E.
hasNotableAlbum
chosen
Indicates that an entity (typically a musical artist or group) is associated with one or more albums that are considered notable or significant.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26c8ffe490819085e17a59638932fa |
completed | June 8, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 8:50 p.m.