Triple
T32314693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | August Storm offensive |
E825599
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet–Japanese War battle |
C7832
|
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: Soviet–Japanese War battle Context triple: [August Storm offensive, instanceOf, Soviet–Japanese War battle]
-
A.
Soviet–Finnish War
The Soviet–Finnish War, also known as the Winter War (1939–1940), was a conflict in which the Soviet Union invaded Finland to secure territory and strategic depth, facing unexpectedly strong Finnish resistance in harsh winter conditions.
-
B.
Japanese war
Japanese war is a conceptual class representing organized, large-scale armed conflicts involving Japan, encompassing their political causes, military strategies, cultural impacts, and historical consequences.
-
C.
battle of the Genpei War
A battle of the Genpei War is a specific military engagement between the Taira and Minamoto clans during Japan’s 1180–1185 civil conflict, characterized by its participants, location, tactics, outcome, and impact on the war’s progression.
-
D.
Soviet campaign
chosen
A Soviet campaign is a coordinated series of military, political, or propaganda operations conducted by the Soviet Union to achieve strategic objectives over a defined period and theater.
-
E.
battle of the Russian conquest of Siberia
A battle of the Russian conquest of Siberia is a military engagement between Russian expansionist forces and indigenous or rival powers that occurred during Russia’s gradual annexation and control of Siberian territories from the late 16th to the 18th century.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:46 a.m.