Triple
T13438287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberkommando der Luftwaffe |
E320287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Luftwaffe command structure |
C32086
|
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: Luftwaffe command structure Context triple: [Oberkommando der Luftwaffe, instanceOf, Luftwaffe command structure]
-
A.
Luftwaffe command position
A Luftwaffe command position is an organizational role within the German air force hierarchy responsible for directing air operations, managing resources, and implementing strategic and tactical decisions.
-
B.
Luftwaffe wing
A Luftwaffe wing is a major operational air unit of the German Air Force, typically composed of several squadrons or groups equipped and organized to perform specific missions such as air defense, strike, or reconnaissance.
-
C.
Luftwaffe air fleet
A Luftwaffe air fleet is a major operational formation of the German Air Force, comprising multiple air corps and support units organized to conduct large-scale air operations within a designated theater.
-
D.
Luftwaffe bomber wing
A Luftwaffe bomber wing is a large, operational German air force unit composed of multiple bomber groups, responsible for planning and executing coordinated bombing missions.
-
E.
Wehrmacht organization
chosen
The Wehrmacht organization is a structured representation of the hierarchical, functional, and administrative components of Nazi Germany’s unified armed forces, including their command chains, unit types, and operational relationships.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:40 p.m.