Triple
T35502589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twin‑Pac |
E1026053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | dual‑pack engine system |
C62215
|
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: dual‑pack engine system Context triple: [Twin‑Pac, instanceOf, dual‑pack engine system]
-
A.
dual overhead camshaft engine
A dual overhead camshaft engine is an internal combustion engine design that uses two camshafts per cylinder bank, mounted above the cylinders, to independently operate intake and exhaust valves for improved performance and efficiency.
-
B.
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.
-
C.
H‑type engine
An H-type engine is an internal combustion engine configuration featuring two horizontally opposed engines stacked vertically and connected to a common crankshaft system, forming an "H" shape to provide compact, high-power output.
-
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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.