Triple
T24423883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kreisleiter |
E615801
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mid-level Nazi Party official |
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: mid-level Nazi Party official Context triple: [Kreisleiter, instanceOf, mid-level Nazi Party official]
-
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.
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.
-
C.
Bavarian civil servant
A Bavarian civil servant is a public-sector employee working within the administrative, legal, or regulatory institutions of the Free State of Bavaria, responsible for implementing laws, delivering public services, and upholding regional and federal regulations.
-
D.
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.
-
E.
NKVD officer
An NKVD officer is a member of the Soviet Union’s internal security and secret police organization responsible for intelligence, political repression, and enforcement of state control during the Stalinist era.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:14 a.m.