Triple

T17482052
Position Surface form Disambiguated ID Type / Status
Subject Operation Quicksilver E425684 entity
Predicate instanceOf P0 FINISHED
Object Allied deception plan C16897 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: Allied deception plan
Context triple: [Operation Quicksilver, instanceOf, Allied deception plan]
  • A. World War II military plan chosen
    A World War II military plan is a strategically designed, time-bound set of coordinated operations and resource allocations intended to achieve specific political and military objectives within the context of the global conflict.
  • B. 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.
  • C. Cold War operation
    A Cold War operation is a covert or overt mission conducted by a state or its proxies during the Cold War era to advance strategic, ideological, or geopolitical objectives without escalating into full-scale direct conflict between superpowers.
  • D. Nazi military operation
    A Nazi military operation is a planned and coordinated action conducted by the armed forces of Nazi Germany to achieve specific strategic, tactical, or political objectives during its period of rule, particularly in World War II.
  • E. World War II resistance operation
    A World War II resistance operation is a covert, organized action conducted by underground groups in occupied territories to sabotage enemy forces, gather intelligence, and support Allied war efforts.
  • 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_69d889dccf7481909264a1844a2e9100 completed April 10, 2026, 5:25 a.m.
Created at: April 10, 2026, 5:48 a.m.