Triple
T17733443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl Heinrich Loeser |
E442646
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nuremberg defendant |
C39614
|
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: Nuremberg defendant Context triple: [Karl Heinrich Loeser, instanceOf, Nuremberg defendant]
-
A.
Krupp Trial defendant
A Krupp Trial defendant is an individual, typically an executive or manager of the Krupp industrial conglomerate, prosecuted in the post–World War II Nuremberg Military Tribunals for war crimes and crimes against humanity related to armaments production, exploitation of forced labor, and support of Nazi aggression.
-
B.
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.
-
C.
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.
-
D.
A級戦犯被告人
A級戦犯被告人とは、第二次世界大戦後の極東国際軍事裁判において「平和に対する罪」など最も重大な戦争犯罪で訴追された日本および連合国側の指導的立場にあった被告人を指す。
-
E.
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.
- F. None of above. chosen
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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:08 a.m.