Triple
T6062386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish Ghetto Police |
E135064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Holocaust-related organization |
C19853
|
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: Holocaust-related organization Context triple: [Jewish Ghetto Police, instanceOf, Holocaust-related organization]
-
A.
organization aiding Jews during the Holocaust
An organization aiding Jews during the Holocaust is a group that covertly or openly provided protection, resources, escape routes, and other life-saving assistance to Jewish individuals and communities persecuted by the Nazi regime and its collaborators.
-
B.
Holocaust-related collection
A Holocaust-related collection is an organized body of materials—such as documents, artifacts, testimonies, and media—that directly pertain to the events, experiences, and historical context of the Holocaust.
-
C.
Holocaust commemoration
Holocaust commemoration is the collective practice of remembering and honoring the victims and survivors of the Holocaust through ceremonies, education, memorials, and cultural expressions to preserve historical truth and prevent future atrocities.
-
D.
Holocaust site
A Holocaust site is a location directly associated with the persecution, deportation, forced labor, or mass murder of Jews and other targeted groups by Nazi Germany and its collaborators during the Holocaust.
-
E.
Holocaust historian
A Holocaust historian is a scholar who researches, analyzes, and interprets the origins, events, experiences, and aftermath of the Holocaust to document its history and preserve its memory.
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:10 p.m.