Triple
T35752091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotus F1 Team |
E1033344
|
entity |
| Predicate | lastRaceWithE22 |
P158575
|
FINISHED |
| Object | 2014 Abu Dhabi Grand Prix |
—
|
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: 2014 Abu Dhabi Grand Prix | Statement: [Lotus F1 Team, lastRaceWithE22, 2014 Abu Dhabi Grand Prix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastRaceWithE22 Context triple: [Lotus F1 Team, lastRaceWithE22, 2014 Abu Dhabi Grand Prix]
-
A.
lastRace
Indicates that one race is the final or most recent race in a sequence or series of races.
-
B.
racedAs
Indicates that one entity participated in a race or competition under the identity, name, or classification of another entity.
-
C.
initiallyRacedWith
Indicates that two entities participated in the same race or competitive event at the beginning of a relevant period or career.
-
D.
lastFormulaOneGrandPrix
chosen
Indicates that one entity is the most recent Formula One Grand Prix event associated with another entity (such as a driver, team, or location).
-
E.
lastPreHiatusRace
Indicates that the referenced race is the final one held immediately before a hiatus or break in a racing schedule or series.
- 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_69f7a197aee48190bbd69f670a3f7721 |
completed | May 3, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.