Triple
T35754010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Beijing ePrix |
E1033391
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Formula E race |
C32788
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Formula E race Context triple: [2014 Beijing ePrix, instanceOf, Formula E race]
-
A.
electric racing series
chosen
An electric racing series is a motorsport competition in which all participating vehicles are powered exclusively by electric propulsion systems, showcasing advancements in electric vehicle technology and sustainable racing.
-
B.
IndyCar race
An IndyCar race is a high-speed, open-wheel motorsport competition held on oval tracks, road courses, or street circuits, where drivers in single-seat cars compete over a set distance or time to finish first under strict technical and sporting regulations.
-
C.
Formula 4 racing series
A Formula 4 racing series is an entry-level, open-wheel motorsport championship designed to bridge the gap between karting and higher single-seater categories by providing young drivers with standardized cars and cost-controlled competition.
-
D.
Formula One Grand Prix
A Formula One Grand Prix is a premier international motor racing event, held on a designated circuit or street track, where teams and drivers compete in highly engineered single-seater cars for championship points.
-
E.
endurance racing series
An endurance racing series is a motorsport competition consisting of long-duration races where teams of drivers, cars, and crews are tested on speed, reliability, strategy, and stamina over extended distances or time periods.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:06 p.m.