Triple
T26389672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull Powertrains (Honda-based) |
E663377
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Formula One power unit program |
C35909
|
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 One power unit program Context triple: [Red Bull Powertrains (Honda-based), instanceOf, Formula One power unit program]
-
A.
Formula One engine
chosen
A Formula One engine is a highly specialized, high-performance internal combustion power unit designed to deliver maximum power, efficiency, and reliability under the extreme conditions of Grand Prix racing.
-
B.
Formula One engineer
A Formula One engineer is a highly specialized professional who designs, optimizes, and manages the performance, reliability, and race strategy of F1 cars using advanced engineering, data analysis, and real-time decision-making.
-
C.
Formula One racing car
A Formula One racing car is a highly specialized, open-wheel, single-seat vehicle engineered for maximum speed, agility, and performance under strict FIA regulations in top-tier motorsport competition.
-
D.
Formula One commercial agreement
A Formula One commercial agreement is a contractual framework that governs the distribution of revenues, commercial rights, and obligations among the sport’s stakeholders, including teams, the commercial rights holder, and governing bodies.
-
E.
Formula One safety car
A Formula One safety car is an official vehicle deployed on track during a race to control the speed of competing cars and ensure safety while hazards are cleared or adverse conditions are managed.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:24 p.m.