Triple
T906732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Lublin |
E19564
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi administrative division |
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: Nazi administrative division Context triple: [District of Lublin, instanceOf, Nazi administrative division]
-
A.
institution of Nazi Germany
An institution of Nazi Germany is any formal organization, governmental body, or structured system established or co-opted by the Nazi regime to implement, enforce, or propagate its totalitarian, racist, and expansionist policies between 1933 and 1945.
-
B.
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.
-
C.
event in Nazi Germany
An event in Nazi Germany is a historically situated occurrence—political, social, military, cultural, or economic—that took place under the National Socialist regime between 1933 and 1945 and contributed to its policies, ideology, or consequences.
-
D.
Nazi Germany expansion
Nazi Germany expansion refers to the aggressive territorial and political enlargement of Germany under Adolf Hitler from 1938 to 1941 through annexations, invasions, and occupations that precipitated and escalated World War II in Europe.
-
E.
state of Germany
A state of Germany is a federal constituent entity (Bundesland) with its own government, constitution, and administrative responsibilities within the Federal Republic of Germany.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.