Triple
T17455755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reno Air Races |
E425022
|
entity |
| Predicate | 2011AccidentConsequence |
P34334
|
FINISHED |
| Object | temporary suspension of the event |
—
|
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: temporary suspension of the event | Statement: [Reno Air Races, 2011AccidentConsequence, temporary suspension of the event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2011AccidentConsequence Context triple: [Reno Air Races, 2011AccidentConsequence, temporary suspension of the event]
-
A.
resultOfAccident
chosen
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
B.
consequenceOfCollision
Indicates that one event, state, or condition occurs as a direct result of a collision between entities.
-
C.
accident
Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
-
D.
causedAccident
Indicates that one entity is responsible for bringing about or initiating an accident involving another entity or situation.
-
E.
accidentType
Indicates the specific category or kind of accident associated with an event or incident.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45141e1d48190b7de9159f1fd71fa |
completed | April 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.