Triple
T10498452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SACM V8X-1500 Hyperbar diesel engine |
E247604
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hyperbar turbocharged diesel engine |
C28134
|
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: hyperbar turbocharged diesel engine Context triple: [SACM V8X-1500 Hyperbar diesel engine, instanceOf, hyperbar turbocharged diesel engine]
-
A.
afterburning turbofan engine
An afterburning turbofan engine is a type of jet engine that combines a turbofan’s efficient core and bypass airflow with an additional combustion stage in the exhaust (afterburner) to provide short-term, significantly increased thrust, typically for military aircraft.
-
B.
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.
-
C.
gas turbine–powered car
A gas turbine–powered car is a road vehicle that uses a gas turbine engine, rather than a conventional piston engine, to convert fuel into mechanical power for propulsion.
-
D.
multi-fuel engine
A multi-fuel engine is a power unit designed to operate efficiently on more than one type of fuel, such as gasoline, diesel, ethanol, or alternative fuels, without requiring major mechanical modifications.
-
E.
turbofan engine
A turbofan engine is a type of air-breathing jet engine that uses a large fan driven by a gas turbine to produce thrust through both accelerated bypass air and exhaust gases for efficient high-speed propulsion.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:25 p.m.