Triple
T35752541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 German Grand Prix |
E1033353
|
entity |
| Predicate | constructorChampionThatSeason |
P147637
|
FINISHED |
| Object | Mercedes |
—
|
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: Mercedes | Statement: [2016 German Grand Prix, constructorChampionThatSeason, Mercedes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructorChampionThatSeason Context triple: [2016 German Grand Prix, constructorChampionThatSeason, Mercedes]
-
A.
worldConstructorsChampionThatSeason
chosen
Indicates that the subject was the Constructors' Champion in the specified racing season.
-
B.
isRecognizedAsChampionForSeason
Indicates that an entity is officially acknowledged as the champion for a specific season.
-
C.
memberChampion
Indicates that an entity serves as the champion or primary representative for a particular member within a group or organization.
-
D.
leagueOfChampion
Indicates that an entity is the league or competition in which a given champion or titleholder competes or holds their status.
-
E.
constructorDebutSeason
Indicates the first competitive season in which a particular constructor participated.
- 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_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:06 p.m.