Triple
T36045622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Leclerc |
E1042662
|
entity |
| Predicate | firstF1PolePosition |
P199926
|
FINISHED |
| Object | 2019 Bahrain Grand Prix |
E99207
|
NE 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: 2019 Bahrain Grand Prix | Statement: [Charles Leclerc, firstF1PolePosition, 2019 Bahrain Grand Prix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstF1PolePosition Context triple: [Charles Leclerc, firstF1PolePosition, 2019 Bahrain Grand Prix]
-
A.
firstPolePositionDriver
Indicates the driver who achieved the very first pole position in a given racing event or series.
-
B.
firstF1PolePositionSeason
chosen
Indicates the season in which a driver achieved their first Formula 1 pole position.
-
C.
achievedPolePositionAt
Indicates that an entity secured the top starting position (pole position) at a specified event or location.
-
D.
achievedFirstF1PodiumWith
Indicates that one entity secured their first-ever Formula 1 podium finish while driving for or in association with the other entity.
-
E.
firstF1PodiumPosition
Indicates the finishing position at which an entity achieved its first-ever podium result in a Formula 1 race.
- F. None of above.
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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38cb9d5a6c81909fe53eefd6ff29d7 |
completed | June 22, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.