Triple
T33678698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 22nd Luftwaffe Field Division |
E862833
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Luftwaffe field division |
C59235
|
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 field division Context triple: [22nd Luftwaffe Field Division, instanceOf, Luftwaffe field division]
-
A.
Luftwaffe Field Division
chosen
The Luftwaffe Field Division was a German World War II ground combat unit formed from surplus Luftwaffe personnel to serve as infantry under army command, typically with limited training and effectiveness.
-
B.
Luftwaffe division
A Luftwaffe division is a large, organized military formation of Nazi Germany’s air force, typically comprising multiple air wings and support units tasked with conducting and supporting aerial operations.
-
C.
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.
-
D.
Wehrmacht army detachment
A Wehrmacht army detachment was a flexible, temporary German World War II field formation, typically larger than a corps but smaller than a full army, created to control specific operational sectors or ad hoc groupings of units.
-
E.
Wehrmacht Heer unit
A Wehrmacht Heer unit is a military formation of Nazi Germany’s army (Heer), organized at various echelons (e.g., squad, company, battalion, division) to conduct land-based combat and support operations during World War II.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:43 a.m.