Triple
T15676778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Office |
E377462
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wehrmacht institution |
C32086
|
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 institution Context triple: [Army Office, instanceOf, Wehrmacht institution]
-
A.
Wehrmacht organization
chosen
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:16 a.m.