Triple
T28107480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2004 Formula One World Championship |
E710401
|
entity |
| Predicate | driversChampionPoles |
P57362
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [2004 Formula One World Championship, driversChampionPoles, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: driversChampionPoles Context triple: [2004 Formula One World Championship, driversChampionPoles, 8]
-
A.
driversChampionWins
Indicates the number of championship titles won by a particular driver.
-
B.
driversChampionships
Indicates the number of drivers’ championship titles an entity has won or is associated with.
-
C.
driversChampionshipWin
Indicates that a driver has won the overall drivers’ championship title in a given racing series or season.
-
D.
driversChampionMargin
Indicates the points difference by which the drivers’ champion finished ahead of the next-best competitor in the championship standings.
-
E.
totalPolePositions
chosen
Indicates the total number of times an entity has achieved pole position in qualifying or starting order across all relevant events.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 9:09 p.m.