Triple
T29780385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chuck Schuldiner |
E755497
|
entity |
| Predicate | notableAlbumWithDeath |
P31992
|
FINISHED |
| Object |
Symbolic
Symbolic is a 1995 technical and melodic death metal album by Death, widely regarded as one of the genre’s most influential and sophisticated releases.
|
E1883648
|
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: Symbolic | Statement: [Chuck Schuldiner, notableAlbumWithDeath, Symbolic]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Symbolic Triple: [Chuck Schuldiner, notableAlbumWithDeath, Symbolic]
Generated description
Symbolic is a 1995 technical and melodic death metal album by Death, widely regarded as one of the genre’s most influential and sophisticated releases.
Provenance (5 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_6a03809725bc81909c8b61d72d72ca2b |
completed | May 12, 2026, 7:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26c8ffe490819085e17a59638932fa |
completed | June 8, 2026, 1:52 p.m. |
| NEDg | Description generation | batch_6a26cda9e7b88190861c905b18256801 |
completed | June 8, 2026, 2:11 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a26d3faa9d08190aa5f45736d43db74 |
completed | June 8, 2026, 2:38 p.m. |
Created at: April 28, 2026, 8:50 p.m.