Triple
T35053519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English Channel 1944 |
E1011397
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European theater of World War II |
C443
|
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: European theater of World War II Context triple: [English Channel 1944, instanceOf, European theater of World War II]
-
A.
theater of World War II
chosen
The theater of World War II is a conceptual class representing a distinct geographic region and operational context in which military campaigns, battles, and strategic activities of the war were planned, conducted, and coordinated.
-
B.
European war
A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
-
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 rear area
A World War II rear area is the zone behind the front lines where military forces organized logistics, supply, administration, medical care, training, and security operations to support combat units at the front.
-
E.
Eastern Front campaign
The Eastern Front campaign is a large-scale military operation or series of operations conducted on the eastern theater of war, typically involving prolonged, high-intensity ground combat across vast territories between major opposing powers.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.