Triple
T34038378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuff Hedeman |
E872869
|
entity |
| Predicate | sufferedInjuryFrom |
P14656
|
FINISHED |
| Object | Bodacious |
—
|
NE NERFINISHED |
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: Bodacious | Statement: [Tuff Hedeman, sufferedInjuryFrom, Bodacious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedInjuryFrom Context triple: [Tuff Hedeman, sufferedInjuryFrom, Bodacious]
-
A.
injuredIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
-
B.
causeOfInjury
chosen
Indicates that one entity is the source or reason that another entity sustained an injury.
-
C.
hasPlaceOfInjury
Indicates that an injury occurred at a specific place or location.
-
D.
hasInjuredPerson
Indicates that an entity has a person who has been harmed or injured associated with it.
-
E.
allegedInjury
Indicates that an injury is claimed or asserted to have occurred, typically without being legally or factually established.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.