Triple
T26461728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 Austrian Grand Prix |
E665655
|
entity |
| Predicate | defendingRaceWinnerStatus |
P168572
|
FINISHED |
| Object | retired |
—
|
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: retired | Statement: [2020 Austrian Grand Prix, defendingRaceWinnerStatus, retired]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendingRaceWinnerStatus Context triple: [2020 Austrian Grand Prix, defendingRaceWinnerStatus, retired]
-
A.
defendingRaceWinner
chosen
Indicates that an entity is the current titleholder who won the previous edition of a race and is thus defending that victory in the present event.
-
B.
raceStatus
Indicates the current state or progress of an entity’s participation in a race or competitive event.
-
C.
raceWon
Indicates that one participant has achieved victory in a race or competitive event over others.
-
D.
notableRaceStatus
Indicates that an entity holds a distinguished or significant status in the context of a particular race or racing event.
-
E.
championshipStatus
Indicates the competitive or title-holding state of an entity within a championship or league context.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 12:13 a.m.