Triple
T33045383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1970 Dutch Grand Prix |
E845579
|
entity |
| Predicate | fatalAccidentCorner |
P176386
|
FINISHED |
| Object | Tunnel Oost |
—
|
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: Tunnel Oost | Statement: [1970 Dutch Grand Prix, fatalAccidentCorner, Tunnel Oost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fatalAccidentCorner Context triple: [1970 Dutch Grand Prix, fatalAccidentCorner, Tunnel Oost]
-
A.
fatalAccident
Indicates that an accident resulted in at least one death.
-
B.
fatalAccidentLap
Indicates that a fatal accident occurred during a specific lap in a race or similar sequential event.
-
C.
fatalAccidentDriver
Indicates that the subject is the driver involved in an accident that resulted in at least one fatality.
-
D.
accident
Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
-
E.
causedAccident
Indicates that one entity is responsible for bringing about or initiating an accident involving another entity or situation.
- F. None of above. chosen
Provenance (4 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 1:24 a.m.