Triple
T26515579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daniil Kvyat |
E669802
|
entity |
| Predicate | replacedByDriverAtRedBullRacing |
P170351
|
FINISHED |
| Object | Max Verstappen |
—
|
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: Max Verstappen | Statement: [Daniil Kvyat, replacedByDriverAtRedBullRacing, Max Verstappen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByDriverAtRedBullRacing Context triple: [Daniil Kvyat, replacedByDriverAtRedBullRacing, Max Verstappen]
-
A.
replacedDriverAtRedBull
chosen
Indicates that one driver took over another driver's race seat or role at the Red Bull Formula 1 team.
-
B.
rebrandedByRedBull
Indicates that an entity has undergone a rebranding process carried out by the company Red Bull.
-
C.
wasFerrariYoungDriver
Indicates that a person participated in Ferrari’s young driver program or was officially recognized as a Ferrari young driver.
-
D.
f1ReplacementCircuit
Indicates that one circuit functions as a replacement for another circuit, taking over its role or operation.
-
E.
replacedInLineupBy
Indicates that one participant in a lineup is substituted or superseded by another participant in that same lineup.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 1:23 a.m.