Triple
T32821851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Marino Grand Prix |
E839453
|
entity |
| Predicate | sawFatality |
P60623
|
FINISHED |
| Object | Ayrton Senna |
—
|
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: Ayrton Senna | Statement: [San Marino Grand Prix, sawFatality, Ayrton Senna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawFatality Context triple: [San Marino Grand Prix, sawFatality, Ayrton Senna]
-
A.
deathSceneFeature
Indicates that a particular feature, element, or characteristic is present in the scene depicting a character’s death.
-
B.
deathAttracting
Indicates a relationship where one entity’s death draws, lures, or otherwise causes another entity to come closer or be attracted.
-
C.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
D.
notableFatality
chosen
Indicates that an entity is a significant or widely recognized example of a death associated with another entity or event.
-
E.
diesInArmsOf
Indicates that one entity dies while being physically held or embraced by another entity.
- 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_69f3493df9008190a8f5d843dcd77704 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:15 a.m.