Triple
T25996707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emile Griffith vs Benny Paret III |
E646504
|
entity |
| Predicate | causeOfDeathForBennyParet |
P144
|
FINISHED |
| Object | brain injuries from fight |
—
|
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: brain injuries from fight | Statement: [Emile Griffith vs Benny Paret III, causeOfDeathForBennyParet, brain injuries from fight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDeathForBennyParet Context triple: [Emile Griffith vs Benny Paret III, causeOfDeathForBennyParet, brain injuries from fight]
-
A.
frontmanCauseOfDeath
Indicates the cause or circumstances of death of the frontman of a group or band.
-
B.
diedInChildhood
Indicates that the person died before reaching adulthood, during their childhood years.
-
C.
diedOfDiseaseApproximate
Indicates that an entity died from a disease, with the cause or timing known only approximately rather than precisely.
-
D.
hasEponymCauseOfDeath
Indicates that an entity’s cause of death is named after (or eponymously derived from) a particular person or entity.
-
E.
causeOfDeath
chosen
Indicates the specific factor, event, or condition that directly resulted in 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 22, 2026, 8:58 a.m.