Triple
T26461734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 Austrian Grand Prix |
E665655
|
entity |
| Predicate | safetyCarDriver |
P161011
|
FINISHED |
| Object | Bernd Mayländer |
—
|
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: Bernd Mayländer | Statement: [2020 Austrian Grand Prix, safetyCarDriver, Bernd Mayländer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyCarDriver Context triple: [2020 Austrian Grand Prix, safetyCarDriver, Bernd Mayländer]
-
A.
safetyCarUsed
Indicates that a safety car was deployed and used during an event or activity.
-
B.
safetyCarSupplier
Indicates that one entity serves as the provider or manufacturer of safety cars for another entity or event.
-
C.
safetyCarLapRecordHolder
Indicates that one entity holds the record for the most notable or fastest performance during a lap completed under safety car conditions in a race.
-
D.
safetyCarPossible
Indicates that conditions are such that deploying a safety car is a valid or allowable option.
-
E.
safetyCarStart
Indicates that a safety car period has begun, initiating the deployment of the safety car onto the track.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612956424819083b0e451342a5811 |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 12:13 a.m.