Triple
T28990872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferrari V6 turbo hybrid |
E736022
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hybrid power unit |
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: hybrid power unit Context triple: [Ferrari V6 turbo hybrid, instanceOf, hybrid power unit]
-
A.
hybrid powertrain technology
Hybrid powertrain technology integrates an internal combustion engine with one or more electric motors and a battery system to optimize fuel efficiency, reduce emissions, and enhance vehicle performance through intelligent power management.
-
B.
gasoline-electric hybrid system
A gasoline-electric hybrid system is a powertrain that combines an internal combustion engine with one or more electric motors and a battery to improve fuel efficiency, reduce emissions, and optimize vehicle performance.
-
C.
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.
-
D.
H-24 engine
An H-24 engine is a 24-cylinder internal combustion engine arranged in an "H" configuration, effectively combining two horizontally opposed 12-cylinder engines to drive a common output shaft.
-
E.
twin-turbocharged engine
A twin-turbocharged engine is an internal combustion engine equipped with two turbochargers working together—either in parallel or sequentially—to increase air intake, boost power output, and improve overall performance and efficiency.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 9:25 a.m.