Triple
T1659222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Reinhard |
E35866
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of the Holocaust |
C3624
|
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: component of the Holocaust Context triple: [Operation Reinhard, instanceOf, component of the Holocaust]
-
A.
component of the Third Reich
chosen
A component of the Third Reich is any organizational, institutional, territorial, or ideological element that contributed to the structure, operation, or objectives of Nazi Germany between 1933 and 1945.
-
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 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.
-
D.
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.
-
E.
component of Judaism
A component of Judaism is a fundamental element—such as belief, practice, text, institution, or cultural tradition—that collectively shapes and expresses Jewish religious life and identity.
- 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_69a88606aa808190aa0b421b4271f220 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:29 p.m.