Triple
T37942955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German SS and police leadership in Latvia |
E946534
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | SS and Police Leader command |
C21481
|
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: SS and Police Leader command Context triple: [German SS and police leadership in Latvia, instanceOf, SS and Police Leader command]
-
A.
police leader
A police leader is a senior law enforcement official responsible for setting strategic direction, making critical operational decisions, and guiding officers to uphold public safety, legal standards, and community trust.
-
B.
Einsatzkommando commander
An Einsatzkommando commander is the officer in charge of a mobile Nazi SS death squad, responsible for organizing, directing, and overseeing mass shootings and other atrocities in occupied territories during World War II.
-
C.
SS leader
chosen
An SS leader is a high-ranking official within the Nazi Schutzstaffel responsible for directing and enforcing the regime’s ideological, military, and security policies, often including the planning and execution of war crimes and atrocities.
-
D.
military police command
A military police command is an organizational unit within the armed forces responsible for law enforcement, security operations, discipline, and order among military personnel and installations.
-
E.
SS officer
An SS officer is a member of the Schutzstaffel, the paramilitary organization of Nazi Germany responsible for enforcing Nazi ideology, overseeing concentration and extermination camps, and perpetrating widespread war crimes and crimes against humanity during World War II.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.