Triple
T1279232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish capitulation at Hel |
E27285
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the invasion of Poland |
C6009
|
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: event in the invasion of Poland Context triple: [Polish capitulation at Hel, instanceOf, event in the invasion of Poland]
-
A.
Polish military history event
chosen
A Polish military history event is a significant occurrence involving Poland’s armed forces—such as battles, campaigns, uprisings, operations, or strategic decisions—that influenced the course of Poland’s national or military development.
-
B.
World War II event
A World War II event is a historically significant occurrence between 1939 and 1945 that directly influenced the political, military, social, or economic course of the global conflict.
-
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.
event in the Second Sino-Japanese War
An event in the Second Sino-Japanese War is a specific historical occurrence—such as a battle, campaign, political decision, or diplomatic incident—that took place between 1937 and 1945 within the broader conflict between China and Japan.
-
E.
phase of World War II
A phase of World War II is a distinct, time-bounded period of the conflict characterized by specific strategic objectives, major campaigns, and shifts in military, political, or economic conditions.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
Created at: March 1, 2026, 7:50 p.m.