Triple
T850898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Berlin |
E18382
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II naval operation |
C873
|
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 operation Context triple: [Operation Berlin, instanceOf, World War II naval operation]
-
A.
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.
-
B.
World War II military formation
A World War II military formation is an organized grouping of military units—such as divisions, corps, or armies—structured and deployed by a nation’s armed forces during the Second World War to conduct coordinated combat and support operations.
-
C.
World War II event
chosen
A World War II event is a historically significant occurrence between 1939 and 1945 that directly influenced the political, military, social, or economic course of the global conflict.
-
D.
amphibious invasion
An amphibious invasion is a coordinated military operation in which armed forces assault a hostile or potentially hostile shore by deploying troops, vehicles, and equipment from the sea onto land.
-
E.
World War II weapon
A World War II weapon is any tool, device, or system—ranging from small arms and artillery to aircraft, naval vessels, and emerging technologies like rockets and atomic bombs—designed and employed by nations between 1939 and 1945 to inflict damage, gain strategic advantage, or defend against enemy forces.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:38 p.m.