Triple
T32220481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wehrkreis VI |
E823050
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wehrkreis |
C23498
|
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: Wehrkreis Context triple: [Wehrkreis VI, instanceOf, Wehrkreis]
-
A.
German military district
chosen
A German military district is a regional administrative and organizational unit of the German armed forces responsible for local command, logistics, personnel management, and military infrastructure within its designated area.
-
B.
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.
-
C.
military district of the Holy Roman Empire
A military district of the Holy Roman Empire was an administrative and territorial unit organized primarily for defense and military command, grouping various imperial estates under a regional military structure.
-
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 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.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:38 a.m.