Triple
T20103572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nettuno V6 |
E496609
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | twin-turbocharged engine |
C42854
|
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: twin-turbocharged engine Context triple: [Nettuno V6, instanceOf, twin-turbocharged engine]
-
A.
hyperbar turbocharged diesel engine
A hyperbar turbocharged diesel engine is an internal combustion engine that uses a high-pressure turbocharging system, often with multiple compressor stages, to significantly increase intake air density and boost power, efficiency, and performance over conventional turbocharged diesels.
-
B.
V12 engine
A V12 engine is a twelve-cylinder internal combustion engine with two banks of six cylinders arranged in a V configuration around a common crankshaft, providing smooth, high-power performance.
-
C.
V-twin engine
A V-twin engine is a two-cylinder internal combustion engine in which the cylinders are arranged in a V configuration around a common crankshaft, typically used in motorcycles and some small vehicles for a balance of torque, compactness, and distinctive sound.
-
D.
W-configuration engine
A W-configuration engine is an internal combustion engine with four cylinder banks arranged in a "W" shape around the crankshaft, effectively combining two narrow-angle V engines to create a compact, high-output powerplant.
-
E.
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.
- F. None of above. chosen
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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:27 p.m.