Triple
T16487786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nationaler Verteidigungsrat der DDR |
E400491
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Militärisches Führungsorgan |
C298
|
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: Militärisches Führungsorgan Context triple: [Nationaler Verteidigungsrat der DDR, instanceOf, Militärisches Führungsorgan]
-
A.
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.
-
B.
military organization
chosen
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
C.
military political organ
A military political organ is an institutional body within the armed forces responsible for overseeing political education, ideological control, and party or state loyalty among military personnel.
-
D.
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.
-
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.
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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:13 a.m.