Triple
T28990958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 Austrian Grand Prix |
E736023
|
entity |
| Predicate | fastestLapPointsAwarded |
P109349
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [2022 Austrian Grand Prix, fastestLapPointsAwarded, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fastestLapPointsAwarded Context triple: [2022 Austrian Grand Prix, fastestLapPointsAwarded, 1]
-
A.
fastestLapBonusPoints
chosen
Indicates that bonus points are awarded to an entity for achieving the fastest lap in a given event or context.
-
B.
fastestLapLapNumber
Indicates the specific lap number on which the fastest lap was achieved in a race.
-
C.
grandPrixFastestLaps
Indicates the relationship where a driver records the fastest lap time during a specific Grand Prix race.
-
D.
fastestLapDriverCountry
Indicates the country associated with the driver who recorded the fastest lap in a given race or session.
-
E.
fastestLapTime
Indicates the shortest recorded time an entity achieved to complete a single lap in a given context or event.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65f7d3b5c8190937aaddff2879989 |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:25 a.m.