Triple
T13180386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Electric CT7 |
E313706
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | turboshaft engine family |
C14076
|
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: turboshaft engine family Context triple: [General Electric CT7, instanceOf, turboshaft engine family]
-
A.
aircraft engine family
A family of aircraft engines is a group of closely related engine models that share a common core design, architecture, and components but differ in specific configurations, performance levels, or applications.
-
B.
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.
-
C.
military aircraft engine
A military aircraft engine is a high-performance propulsion system designed to power combat and support aircraft, optimized for thrust, reliability, maneuverability, and operation under extreme conditions.
-
D.
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.
-
E.
gas turbine engine
chosen
A gas turbine engine is a continuous-flow internal combustion engine that compresses air, mixes it with fuel, burns the mixture, and expands the hot gases through turbine and nozzle stages to produce mechanical power or thrust.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:14 p.m.