Triple
T20164889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Macho |
E491802
|
entity |
| Predicate | fakesDeathBy |
P11798
|
FINISHED |
| Object | riding a shark with dynamite into a volcano |
—
|
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: riding a shark with dynamite into a volcano | Statement: [El Macho, fakesDeathBy, riding a shark with dynamite into a volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fakesDeathBy Context triple: [El Macho, fakesDeathBy, riding a shark with dynamite into a volcano]
-
A.
fakedOwnDeath
Indicates that an entity deliberately staged or pretended their own death to deceive others.
-
B.
reasonForFakedDeath
Indicates the motive or justification behind an entity’s decision to fake or stage their own death.
-
C.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
D.
deathMethod
chosen
Indicates the specific way or means by which a death occurred.
-
E.
deathLeadsTo
Indicates that one entity’s death causes, results in, or brings about another event, state, or condition.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6684376408190a68890ab48fa5424 |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.