Triple
T38152332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daugavpils ghetto |
E952788
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi ghetto in Latvia |
C47723
|
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 ghetto in Latvia Context triple: [Daugavpils ghetto, instanceOf, Nazi ghetto in Latvia]
-
A.
World War II ghetto
chosen
A World War II ghetto was a segregated, enclosed urban district where Nazi authorities forcibly confined Jews (and sometimes other targeted groups) under overcrowded, impoverished, and brutal conditions as part of their broader system of persecution and genocide.
-
B.
Latvian Jew
A Latvian Jew is a person of Jewish ethnicity, culture, or religion who has historical, familial, or personal ties to Latvia.
-
C.
Judenrat
The Judenrat was a Jewish council established by Nazi authorities in occupied territories during World War II to administer and enforce German orders within Jewish communities, often under coercion and threat of violence.
-
D.
Warsaw Ghetto inmate
A Warsaw Ghetto inmate is a Jewish person forcibly confined within the Nazi-established Warsaw Ghetto during World War II, enduring extreme overcrowding, starvation, persecution, and the constant threat of deportation and death.
-
E.
Jewish ghetto inhabitant
A Jewish ghetto inhabitant is a Jewish person forcibly confined to a segregated, restricted urban district under discriminatory laws or occupation, typically facing overcrowding, deprivation, and persecution.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.