Triple
T34704932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish territories directly incorporated into the Reich |
E1000475
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II historical region |
C61941
|
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: World War II historical region Context triple: [Polish territories directly incorporated into the Reich, instanceOf, World War II historical region]
-
A.
World War II-era state
A World War II-era state is a sovereign political entity operating between roughly 1933 and 1945 whose institutions, economy, military, and society were shaped by the global conflict, wartime alliances, and total war mobilization.
-
B.
World War II site
A World War II site is a historically significant location directly associated with events, operations, or impacts of the Second World War, preserved or recognized for its cultural, military, or memorial value.
-
C.
World War II front
A World War II front is a large-scale, geographically defined theater of military operations where opposing forces engaged in sustained combat and strategic maneuvers during the Second World War.
-
D.
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.
-
E.
aspect of World War II
An aspect of World War II is a distinct thematic component—such as military strategy, political leadership, home-front life, technology, or ideology—that helps explain how the conflict was conducted, experienced, and remembered.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.