Triple
T10975741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Valkyrie |
E259364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II military operation 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: World War II military operation plan Context triple: [Operation Valkyrie, instanceOf, World War II military operation 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 campaign
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.
-
C.
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.
-
D.
World War II project
A World War II project is a structured investigation or creative work that explores specific aspects of the Second World War—such as events, people, technology, or impacts—using historical sources to analyze and present findings.
-
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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:24 p.m.