Triple
T7147054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaolzie annexation of 1938 |
E166594
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish–Czechoslovak territorial dispute |
C8411
|
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: Polish–Czechoslovak territorial dispute Context triple: [Zaolzie annexation of 1938, instanceOf, Polish–Czechoslovak territorial dispute]
-
A.
Polish–Russian war
The Polish–Russian war refers to a series of historical military conflicts between Poland (or the Polish–Lithuanian Commonwealth) and Russia (including Muscovy and later the Russian Empire) over territorial control, political influence, and regional dominance in Eastern Europe.
-
B.
disputed territory
A disputed territory is a geographic area over which two or more parties claim sovereignty or control, without mutual agreement on its legal or political status.
-
C.
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.
-
D.
border conflict
chosen
A border conflict is a dispute between neighboring states or groups over the ownership, control, or demarcation of a shared territorial boundary.
-
E.
Habsburg–Ottoman War
The Habsburg–Ottoman War is a conceptual class representing the series of military conflicts between the Habsburg Monarchy and the Ottoman Empire, encompassing their political, territorial, and religious struggles across Central and Eastern Europe from the 16th to the 18th centuries.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:46 p.m.