Triple
T30721509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XXVII (2nd Royal Württemberg and Saxon) Reserve Corps |
E782166
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corps of the German Army |
C57754
|
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: corps of the German Army Context triple: [XXVII (2nd Royal Württemberg and Saxon) Reserve Corps, instanceOf, corps of the German Army]
-
A.
branch of the German Army
A branch of the German Army is a specialized organizational subdivision responsible for a distinct set of military functions, capabilities, and operational roles within the overall land forces structure.
-
B.
Wehrmacht corps
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.
army of the Wehrmacht
The army of the Wehrmacht was Nazi Germany’s unified land warfare force from 1935 to 1945, responsible for conducting large-scale military operations and invasions across Europe and beyond during World War II.
-
D.
Prussian Army corps
A Prussian Army corps was a large, semi-independent military formation within the Prussian Army, typically composed of multiple divisions and supporting units, organized for operational-level command and control in war.
-
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. chosen
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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:36 p.m.