Triple
T21108345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heer |
E520109
|
entity |
| Predicate | causeOfDeathInLegend |
P100625
|
FINISHED |
| Object | poisoning |
—
|
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: poisoning | Statement: [Heer, causeOfDeathInLegend, poisoning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDeathInLegend Context triple: [Heer, causeOfDeathInLegend, poisoning]
-
A.
legendaryCauseOfDeath
chosen
Indicates a legendary or mythic account of how an entity died, as opposed to a historically verified cause of death.
-
B.
deifiedPersonDeathCause
Indicates the cause or manner of death of the person who is venerated or treated as a deity.
-
C.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
D.
legendaryDeath
Indicates a death that is renowned or celebrated in stories or history, often marked by extraordinary circumstances or lasting fame.
-
E.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
- 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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e720ffa998819082db225363ac3b23 |
completed | April 21, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:54 p.m.