Triple

T22848417
Position Surface form Disambiguated ID Type / Status
Subject Operation Harpoon E566286 entity
Predicate instanceOf P0 FINISHED
Object World War II naval convoy operation C32442 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 convoy operation
Context triple: [Operation Harpoon, instanceOf, World War II naval convoy operation]
  • 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 Allied operation chosen
    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.
  • C. 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.
  • D. World War II commando raid
    A World War II commando raid is a small-scale, highly planned military operation conducted by specially trained troops to infiltrate enemy territory, achieve a specific tactical or strategic objective, and withdraw quickly, often relying on surprise and stealth.
  • 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_69e2458750b481908a8e4cf4609cc6cf completed April 17, 2026, 2:36 p.m.
Created at: April 17, 2026, 3:36 p.m.