Triple
T2358609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinrich Gley |
E47215
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi perpetrator |
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: Nazi perpetrator Context triple: [Heinrich Gley, instanceOf, Nazi perpetrator]
-
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.
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.
-
C.
war criminal
A war criminal is an individual who has committed serious violations of the laws and customs of war, such as targeting civilians, mistreating prisoners, or using prohibited weapons, and can be held personally responsible under international law.
-
D.
collaborator with Nazi Germany
A collaborator with Nazi Germany is an individual, group, or government that actively cooperated with or supported the policies, military efforts, or occupation authorities of the Third Reich during its period of power, often to gain advantage or out of ideological alignment.
-
E.
mass murderer
A mass murderer is an individual who unlawfully kills multiple people, typically in a single event or closely related series of events, often in a single location.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
Created at: March 4, 2026, 7:55 p.m.