Triple
T9133197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T'Chaka |
E219139
|
entity |
| Predicate | causeOfDeath_MCU |
P144
|
FINISHED |
| Object | killed in bombing orchestrated by Helmut Zemo |
—
|
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: killed in bombing orchestrated by Helmut Zemo | Statement: [T'Chaka, causeOfDeath_MCU, killed in bombing orchestrated by Helmut Zemo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDeath_MCU Context triple: [T'Chaka, causeOfDeath_MCU, killed in bombing orchestrated by Helmut Zemo]
-
A.
causeOfDeath
chosen
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
B.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
C.
reasonForDemise
Indicates the cause, circumstance, or factor that led to an entity’s death or termination.
-
D.
namedAfterCauseOfDeath
Indicates that an entity is named after the cause of death of a person or organism.
-
E.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8dccecc81908d8fc641c419ca6a |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.