Triple
T21049848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilhelm Crohne |
E518547
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi-era judge |
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: Nazi-era judge Context triple: [Wilhelm Crohne, instanceOf, Nazi-era judge]
-
A.
Nuremberg defendant
A Nuremberg defendant is an individual, typically a high-ranking Nazi political, military, or industrial leader, prosecuted before the International Military Tribunal after World War II for crimes against peace, war crimes, and crimes against humanity.
-
B.
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.
-
C.
Nazi hunter
A Nazi hunter is an individual dedicated to identifying, tracking, and bringing to justice former members and collaborators of the Nazi regime for their war crimes and human rights violations.
-
D.
Warsaw Ghetto leader
A Warsaw Ghetto leader is an individual who held a position of authority or influence within the Warsaw Ghetto during Nazi occupation, responsible for organizing resistance, administration, or community survival efforts under extreme persecution.
-
E.
Holocaust perpetrator
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.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:34 p.m.