Triple
T19957397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yer Maun |
E479719
|
entity |
| Predicate | refersToCauseOfDeath |
P144
|
FINISHED |
| Object | racing accident |
—
|
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: racing accident | Statement: [Yer Maun, refersToCauseOfDeath, racing accident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToCauseOfDeath Context triple: [Yer Maun, refersToCauseOfDeath, racing accident]
-
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.
namedAfterCauseOfDeath
Indicates that an entity is named after the cause of death of a person or organism.
-
D.
indirectFatalitiesCause
Indicates a causal relationship where an entity is responsible for deaths that occur indirectly, as a secondary or downstream consequence rather than as the immediate cause.
-
E.
deathCauseUncertainty
Indicates that there is ambiguity, doubt, or lack of definitive information about the cause of death in the relationship being described.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af1b32c81908ebe0e2570ec06a9 |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.