Triple
T12372621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judenrat of Łódź Ghetto |
E295040
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ghetto administration body |
C31370
|
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 administration body Context triple: [Judenrat of Łódź Ghetto, instanceOf, ghetto administration body]
-
A.
Gulag administrative body
The Gulag administrative body is the centralized state organization responsible for planning, managing, and overseeing the operation of forced labor camps within the Soviet penal system.
-
B.
rectorate
The rectorate is the governing body or office of a rector, responsible for the overall academic, administrative, and strategic leadership of a university or higher education institution.
-
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.
Reichskommissariat
A Reichskommissariat was a type of civilian administrative territory established and governed by Nazi Germany in occupied regions during World War II, intended to facilitate political control, economic exploitation, and eventual Germanization.
-
E.
Polish resistance organization
A Polish resistance organization is a clandestine group formed in Poland to oppose and undermine occupying or oppressive regimes through coordinated political, military, and intelligence activities.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:54 p.m.