Triple
T35053518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English Channel 1944 |
E1011397
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II naval operations |
C635
|
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 naval operations Context triple: [English Channel 1944, instanceOf, World War II naval operations]
-
A.
World War II convoy series
A World War II convoy series is a sequence of organized Allied or Axis merchant and naval ship movements, typically identified by a code, that traveled together under escort for mutual protection against enemy attacks during the war.
-
B.
World War II naval disaster
A World War II naval disaster is a catastrophic maritime event during the Second World War in which warships or naval convoys suffered significant loss of life, vessels, or strategic capability due to combat, accidents, or environmental conditions.
-
C.
World War II Allied operation
A World War II Allied operation is a coordinated military campaign or mission planned and executed by the Allied powers to achieve specific strategic, tactical, or logistical objectives against the Axis forces.
-
D.
World War II campaign
chosen
A World War II campaign is a coordinated series of military operations conducted over a specific period and geographic area, aimed at achieving strategic objectives within the broader context of the war.
-
E.
Kriegsmarine operation
A Kriegsmarine operation is a coordinated naval action planned and executed by Nazi Germany’s navy during World War II to achieve specific military, strategic, or logistical objectives at sea.
- 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.