Triple
T2739106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OKH (Oberkommando des Heeres) |
E60705
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German military high command |
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: German military high command Context triple: [OKH (Oberkommando des Heeres), instanceOf, German military high command]
-
A.
branch of the German Army
A branch of the German Army is a specialized organizational subdivision responsible for a distinct set of military functions, capabilities, and operational roles within the overall land forces structure.
-
B.
Nazi Germany military rank
A Nazi Germany military rank represents a specific hierarchical position within the armed forces of the Third Reich, defining an individual's authority, responsibilities, and status in the military structure.
-
C.
German soldiers
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.
Nazi official
A Nazi official is a person who held an administrative, political, or military position within the National Socialist (Nazi) regime in Germany, responsible for implementing and enforcing its totalitarian, racist, and genocidal policies.
-
E.
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.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:56 p.m.