Triple
T13153826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3rd Mountain Division |
E312531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wehrmacht mountain infantry division |
C14618
|
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 mountain infantry division Context triple: [3rd Mountain Division, instanceOf, Wehrmacht mountain infantry division]
-
A.
Wehrmacht infantry division
chosen
A Wehrmacht infantry division was a World War II-era German Army formation composed primarily of foot soldiers, supported by artillery, engineers, and logistical units, organized for sustained ground combat operations.
-
B.
Wehrmacht regiment
A Wehrmacht regiment was a mid-level military unit of Nazi Germany’s armed forces, typically composed of several battalions and supporting elements, responsible for tactical operations within a division.
-
C.
Waffen-SS division
A Waffen-SS division was a large, front-line combat formation of Nazi Germany’s Waffen-SS, combining infantry, armor, and support units under a unified command and ideologically aligned with the SS.
-
D.
Wehrmacht armoured division
A Wehrmacht armoured division was a World War II German military formation combining tanks, mechanized infantry, artillery, and support units to conduct fast, coordinated offensive operations.
-
E.
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.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:11 p.m.