Triple
T16814383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernhard Kühn |
E408702
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wehrmacht personnel |
C2751
|
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 personnel Context triple: [Bernhard Kühn, instanceOf, Wehrmacht personnel]
-
A.
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.
-
B.
Wehrmacht organization
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.
-
C.
German soldiers
chosen
German soldiers are military personnel serving in Germany’s armed forces, historically or presently, who are trained, organized, and equipped to conduct defense and combat operations under German command.
-
D.
Wehrkreis staff
Wehrkreis staff were the administrative and command personnel responsible for managing military districts (Wehrkreise) in Germany, overseeing conscription, training, logistics, and local defense organization.
-
E.
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.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:23 a.m.