Triple
T27900338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl August Hanke |
E705612
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Reichsführer-SS |
C2513
|
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: Reichsführer-SS Context triple: [Karl August Hanke, instanceOf, Reichsführer-SS]
-
A.
Nazi official
chosen
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.
-
B.
Waffen-SS officer
A Waffen-SS officer was a commissioned leader within Nazi Germany’s Waffen-SS, responsible for commanding combat units of this paramilitary organization that was deeply involved in war crimes and atrocities during World War II.
-
C.
Kriegsmarine admiral
A Kriegsmarine admiral is a high-ranking naval officer of Nazi Germany’s World War II navy, responsible for commanding major fleets, naval operations, and strategic maritime planning.
-
D.
member of Nazi inner circle
A member of the Nazi inner circle is a high-ranking, influential individual who directly participated in shaping, directing, and sustaining the core leadership, policies, and operations of the National Socialist regime.
-
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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 6:41 p.m.