Triple
T32010319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead Like Me |
E817381
|
entity |
| Predicate | protagonistOccupationAfterDeath |
P21567
|
FINISHED |
| Object | grim reaper |
—
|
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: grim reaper | Statement: [Dead Like Me, protagonistOccupationAfterDeath, grim reaper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistOccupationAfterDeath Context triple: [Dead Like Me, protagonistOccupationAfterDeath, grim reaper]
-
A.
roleInDeaths
Indicates the role or involvement an entity had in causing, contributing to, or being responsible for one or more deaths.
-
B.
protagonistParentOccupation
Indicates the occupation or job held by the protagonist’s parent in the described context.
-
C.
otherProtagonistOccupation
Indicates that another main character in the narrative has a specific occupation or job role.
-
D.
featuresProtagonistOccupation
chosen
Indicates that the work’s main character has a specified occupation or job role.
-
E.
afterDeathOf
Indicates that one event, state, or condition occurs subsequent to and as a result of the death of a specified entity.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 12:15 a.m.