Triple
T11601602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS and Police Leader Lublin command |
E275143
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional SS and Police Leader command |
C23961
|
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: regional SS and Police Leader command Context triple: [SS and Police Leader Lublin command, instanceOf, regional SS and Police Leader command]
-
A.
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.
-
B.
Nazi SS office
chosen
A Nazi SS office was an administrative and operational unit of the Schutzstaffel responsible for planning, coordinating, and executing the regime’s ideological, security, and genocidal policies.
-
C.
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.
-
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.
Sturmabteilung rank
A Sturmabteilung rank represents a specific hierarchical position and level of authority within the paramilitary wing of the Nazi Party in Germany.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:38 p.m.