Triple
T7177387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lê Văn Tám |
E167353
|
entity |
| Predicate | deathCauseInLegend |
P41523
|
FINISHED |
| Object | self-immolation during attack |
—
|
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: self-immolation during attack | Statement: [Lê Văn Tám, deathCauseInLegend, self-immolation during attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathCauseInLegend Context triple: [Lê Văn Tám, deathCauseInLegend, self-immolation during attack]
-
A.
deifiedPersonDeathCause
Indicates the cause or manner of death of the person who is venerated or treated as a deity.
-
B.
legendaryDeath
chosen
Indicates a death that is renowned or celebrated in stories or history, often marked by extraordinary circumstances or lasting fame.
-
C.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
D.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
E.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
- 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_69c68889a2748190a316c5e65360361a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e9b045c48190b27b2d6f7c11026f |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e74fb0f48190b2ad4dd4efdd241a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:49 p.m.