Triple
T21322778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinz Brückner |
E525662
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defendant in the RuSHA Trial |
C44683
|
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: defendant in the RuSHA Trial Context triple: [Heinz Brückner, instanceOf, defendant in the RuSHA Trial]
-
A.
defendant
A defendant is a person or entity against whom a legal action, criminal charge, or civil lawsuit is brought in a court of law.
-
B.
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.
-
C.
witch trial
A witch trial is a formal legal or quasi-legal proceeding in which individuals are accused, investigated, and judged for alleged practice of witchcraft, often driven by fear, superstition, and social or religious tensions.
-
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.
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.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 4:40 p.m.