Triple
T18135289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bialystok Ghetto Uprising |
E434119
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ghetto uprising |
C39692
|
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: ghetto uprising Context triple: [Bialystok Ghetto Uprising, instanceOf, ghetto uprising]
-
A.
Ghetto-Polizei
Ghetto-Polizei: A specialized police unit operating within or overseeing activities in a segregated, marginalized urban district (ghetto), often associated with oppressive control, surveillance, and enforcement of discriminatory policies.
-
B.
Nazi death marches
Nazi death marches were forced evacuations of concentration camp prisoners on brutal, often lethal marches near the end of World War II, intended to prevent their liberation and conceal evidence of Nazi atrocities.
-
C.
Warsaw Ghetto leader
A Warsaw Ghetto leader is an individual who held a position of authority or influence within the Warsaw Ghetto during Nazi occupation, responsible for organizing resistance, administration, or community survival efforts under extreme persecution.
-
D.
battle of the Polish–Ukrainian War
A battle of the Polish–Ukrainian War is a specific military engagement between Polish and Ukrainian forces during the 1918–1919 conflict over territorial control and national sovereignty in Eastern Europe.
-
E.
ghetto administration body
A ghetto administration body is an authority structure, often imposed or controlled by an external regime, responsible for managing the daily governance, resources, and population regulation within a segregated and marginalized urban district.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:29 a.m.