Triple
T18700137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junkers Jumo diesel engines |
E457225
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aircraft diesel engine family |
C8795
|
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: aircraft diesel engine family Context triple: [Junkers Jumo diesel engines, instanceOf, aircraft diesel 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.
diesel engine family
chosen
A diesel engine family is a group of related diesel engines that share a common basic design, architecture, and components but differ in specific configurations such as displacement, power output, and intended applications.
-
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.
engine family
An engine family is a group of related internal combustion engines that share a common basic design, architecture, and components but may differ in specific configurations, displacements, or performance characteristics.
-
E.
automotive engine family
An automotive engine family is a group of closely related internal combustion engines that share a common basic design, architecture, and components but differ in specific parameters such as displacement, tuning, or fuel system to suit various vehicle applications.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.