Triple
T6857069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landing at Arawe |
E158172
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II amphibious assault |
C341
|
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 amphibious assault Context triple: [Landing at Arawe, instanceOf, World War II amphibious assault]
-
A.
amphibious invasion
chosen
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.
-
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.
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.
-
D.
World War II offensive
A World War II offensive is a coordinated, large-scale military campaign conducted by one or more nations to seize strategic objectives, weaken enemy forces, or shift the balance of the war in a specific theater or front.
-
E.
Pacific War engagement
A Pacific War engagement is a specific military confrontation between opposing forces in the Pacific theater during World War II, encompassing actions in air, sea, and/or land domains.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:21 p.m.