Triple
T26389855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Webber |
E663380
|
entity |
| Predicate | bestChampionshipFinishYear |
P155129
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Mark Webber, bestChampionshipFinishYear, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestChampionshipFinishYear Context triple: [Mark Webber, bestChampionshipFinishYear, 2010]
-
A.
yearOfBestChampionshipFinish
chosen
Indicates the specific year in which an entity achieved its highest (best) finishing position in a championship competition.
-
B.
bestIndy500FinishYear
Indicates the year in which an entity achieved its best (highest) finishing position in the Indianapolis 500 race.
-
C.
bestCupSeasonFinishYear
Indicates the year in which an entity achieved its best (highest) finishing position in a cup competition season.
-
D.
championshipEndYear
Indicates the calendar year in which a particular championship or title-holding period concludes.
-
E.
yearOfBestOpenFinish
Indicates the year in which an entity achieved its best (highest) finishing position in an Open tournament or championship.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610be3e848190b7acb7675e37e1f5 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 11:24 p.m.