Triple
T7531533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Russian Grand Prix |
E178033
|
entity |
| Predicate | polePositionDriverNationality |
P77652
|
FINISHED |
| Object | British |
—
|
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: British | Statement: [2014 Russian Grand Prix, polePositionDriverNationality, British]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: polePositionDriverNationality Context triple: [2014 Russian Grand Prix, polePositionDriverNationality, British]
-
A.
polePositions
Indicates that one entity holds the pole position (starting first) relative to another entity in a competitive event, such as a race.
-
B.
totalPolePositions
Indicates the total number of times an entity has achieved pole position in qualifying or starting order across all relevant events.
-
C.
WorldCupPodiums
Indicates that an entity has achieved a top-three (podium) finish in a FIFA World Cup tournament.
-
D.
totalFormulaOnePodiums
Indicates the total number of times an entity has finished on the podium (top three positions) in Formula One races.
-
E.
positionOnRace
Indicates the relative ranking or placement an entity holds within the context of a race or competitive event.
- F. None of above. chosen
Provenance (4 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8217b1c8190b3db453cee0fc4fd |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f5cea2748190afd607ef93e8d66c |
completed | March 27, 2026, 9:25 p.m. |
Created at: March 27, 2026, 3:47 p.m.