Triple
T35752436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Austrian Grand Prix |
E1033351
|
entity |
| Predicate | precedingRace |
P195064
|
FINISHED |
| Object | 2016 European Grand Prix |
—
|
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: 2016 European Grand Prix | Statement: [2016 Austrian Grand Prix, precedingRace, 2016 European Grand Prix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedingRace Context triple: [2016 Austrian Grand Prix, precedingRace, 2016 European Grand Prix]
-
A.
lastRace
Indicates that one race is the final or most recent race in a sequence or series of races.
-
B.
racedAs
Indicates that one entity participated in a race or competition under the identity, name, or classification of another entity.
-
C.
lastPreHiatusRace
Indicates that the referenced race is the final one held immediately before a hiatus or break in a racing schedule or series.
-
D.
predecessorRiding
Indicates that one entity is riding or mounted on another entity that is its predecessor in some defined sequence or ordering.
-
E.
previousChampionship
Indicates that one entity held a championship title immediately before another entity in a sequence of championships.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
| PDg | Predicate description generation | batch_69fd9fef7aac819089cc88dd3d00296d |
completed | May 8, 2026, 8:33 a.m. |
Created at: May 3, 2026, 4:06 p.m.