Triple
T33409071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LXXXIV Army Corps (acting) |
E855523
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wehrmacht corps-level command |
C13720
|
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: Wehrmacht corps-level command Context triple: [LXXXIV Army Corps (acting), instanceOf, Wehrmacht corps-level command]
-
A.
Wehrmacht high command
The Wehrmacht high command was the central military leadership of Nazi Germany responsible for planning, directing, and coordinating the operations of the German armed forces during the Second World War.
-
B.
Wehrmacht corps
chosen
A Wehrmacht corps was a mid-level German Army formation in World War II, typically commanding several divisions and supporting units to conduct coordinated operations within a larger army structure.
-
C.
Wehrmacht organization
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.
-
D.
corps of the German Army
A corps of the German Army is a large, operational-level military formation typically composed of multiple divisions and supporting units, responsible for conducting sustained, coordinated land operations within a designated theater.
-
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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.