Triple
T10948279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nachrichten-Abteilung 200 |
E258654
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wehrmacht signals unit |
C28602
|
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 signals unit Context triple: [Nachrichten-Abteilung 200, instanceOf, Wehrmacht signals unit]
-
A.
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.
-
B.
Wehrmacht headquarters
The Wehrmacht headquarters was the central command authority of Nazi Germany's unified armed forces, responsible for strategic planning, coordination, and direction of military operations during World War II.
-
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.
German army detachment
A German army detachment is a temporary, task-organized military formation separated from a larger parent unit to conduct specific operations under its own command structure.
-
E.
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.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:23 p.m.