Triple
T8050117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trawniki men |
E187651
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Holocaust perpetrators |
C2514
|
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: Holocaust perpetrators Context triple: [Trawniki men, instanceOf, Holocaust perpetrators]
-
A.
Holocaust perpetrator
chosen
A Holocaust perpetrator is an individual who directly or indirectly participated in planning, facilitating, or carrying out the systematic persecution and mass murder of Jews and other targeted groups by Nazi Germany and its collaborators during the Holocaust.
-
B.
Holocaust denier
A Holocaust denier is a person who rejects, distorts, or minimizes the established historical facts of the Nazi genocide of six million Jews and millions of other victims during World War II, often for ideological or antisemitic reasons.
-
C.
Holocaust survivors
Individuals who endured and lived through the systematic persecution and genocide carried out by Nazi Germany and its collaborators during the Holocaust, often bearing profound physical, emotional, and psychological scars.
-
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.
Nazi death marches
Nazi death marches were forced evacuations of concentration camp prisoners on brutal, often lethal marches near the end of World War II, intended to prevent their liberation and conceal evidence of Nazi atrocities.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:24 p.m.