Triple
T24340444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ralf Schumacher |
E613497
|
entity |
| Predicate | F1BestChampionshipPosition |
P99787
|
FINISHED |
| Object | 4th |
—
|
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: 4th | Statement: [Ralf Schumacher, F1BestChampionshipPosition, 4th]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: F1BestChampionshipPosition Context triple: [Ralf Schumacher, F1BestChampionshipPosition, 4th]
-
A.
bestFormulaOneChampionshipPosition
chosen
Indicates the highest (best) finishing position an entity has ever achieved in a Formula One World Championship season.
-
B.
F1Points
Indicates that an entity has earned or is associated with a specific number of Formula 1 championship points.
-
C.
totalFormulaOnePodiums
Indicates the total number of times an entity has finished on the podium (top three positions) in Formula One races.
-
D.
achievedPolePositionAt
Indicates that an entity secured the top starting position (pole position) at a specified event or location.
-
E.
bestRaceFinishPositionAchievedByDriver
Indicates the best (highest-ranking) race finishing position that a particular driver has ever achieved.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932461ec8190933bf1e56e0f647e |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:57 a.m.