Triple
T10851142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maybach HL42 |
E256147
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II military vehicle engine |
C18933
|
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: World War II military vehicle engine Context triple: [Maybach HL42, instanceOf, World War II military vehicle engine]
-
A.
armored vehicle engine
chosen
An armored vehicle engine is a high-torque, durable power unit designed to reliably propel heavily protected military or security vehicles under demanding operational conditions.
-
B.
World War II weapon
A World War II weapon is any tool, device, or system—ranging from small arms and artillery to aircraft, naval vessels, and emerging technologies like rockets and atomic bombs—designed and employed by nations between 1939 and 1945 to inflict damage, gain strategic advantage, or defend against enemy forces.
-
C.
World War II aircraft
World War II aircraft are military airplanes designed, produced, and deployed between 1939 and 1945 for roles such as fighters, bombers, transports, and reconnaissance in support of the war’s air operations.
-
D.
World War II technology
World War II technology encompasses the advanced weapons, vehicles, communication systems, and scientific innovations developed and deployed during the conflict, which significantly influenced both the war’s outcome and postwar technological progress.
-
E.
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.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:20 p.m.