Triple
T27747771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermann Foertsch |
E702033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | war criminal defendant |
C44647
|
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: war criminal defendant Context triple: [Hermann Foertsch, instanceOf, war criminal defendant]
-
A.
war crime defendant
chosen
A war crime defendant is an individual formally accused of violating the laws and customs of war, such as committing atrocities against civilians, prisoners of war, or other protected persons, and is subject to investigation and trial in a competent court or tribunal.
-
B.
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.
-
C.
war crimes trial
A war crimes trial is a formal legal proceeding in which individuals or groups are prosecuted and judged for violations of the laws and customs of war, such as atrocities against civilians, prisoners of war, or other protected persons.
-
D.
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.
-
E.
warCrime
A warCrime is an unlawful act committed during armed conflict that violates international humanitarian law, such as targeting civilians, mistreating prisoners, or using prohibited weapons.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 4:17 p.m.