Triple
T35752540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 German Grand Prix |
E1033353
|
entity |
| Predicate | driverChampionThatSeason |
P109368
|
FINISHED |
| Object | Nico Rosberg |
—
|
NE NERFINISHED |
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: Nico Rosberg | Statement: [2016 German Grand Prix, driverChampionThatSeason, Nico Rosberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: driverChampionThatSeason Context triple: [2016 German Grand Prix, driverChampionThatSeason, Nico Rosberg]
-
A.
worldConstructorsChampionThatSeason
Indicates that the subject was the Constructors' Champion in the specified racing season.
-
B.
associatedDriverChampion
chosen
Indicates that there is a relationship linking something (such as a season, event, or record) to the driver who is recognized as the champion for that context.
-
C.
isRecognizedAsChampionForSeason
Indicates that an entity is officially acknowledged as the champion for a specific season.
-
D.
memberChampion
Indicates that an entity serves as the champion or primary representative for a particular member within a group or organization.
-
E.
featuredChampion
Indicates that an entity is highlighted or designated as a primary or special champion in a given context or event.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:06 p.m.