Triple
T15843135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2006 Formula One World Championship |
E384146
|
entity |
| Predicate | driversChampionNationality |
P109361
|
FINISHED |
| Object | Spanish |
—
|
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: Spanish | Statement: [2006 Formula One World Championship, driversChampionNationality, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: driversChampionNationality Context triple: [2006 Formula One World Championship, driversChampionNationality, Spanish]
-
A.
driversChampionships
Indicates the number of drivers’ championship titles an entity has won or is associated with.
-
B.
worldDriversChampionNationality
chosen
Indicates the nationality associated with a given world drivers champion.
-
C.
driversChampionshipWin
Indicates that a driver has won the overall drivers’ championship title in a given racing series or season.
-
D.
championTeamDrivers
Indicates that the specified drivers were the official championship-winning drivers for the given team in a particular competition or season.
-
E.
polePositionDriverNationality
Indicates the nationality associated with the driver who secured pole position in a race.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142ea3da08190a9d2d5917f84907c |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005434ed88190baf11c169da3cf29 |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.