Triple
T630513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Tsushima |
E15915
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battle of the Russo-Japanese War |
C647
|
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: battle of the Russo-Japanese War Context triple: [Battle of Tsushima, instanceOf, battle of the Russo-Japanese War]
-
A.
imperial war
Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
-
B.
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.
-
C.
campaign of the Russian Civil War
A campaign of the Russian Civil War is a coordinated series of military operations conducted by opposing factions over a specific region and period, aimed at achieving strategic political and territorial objectives within the broader conflict.
-
D.
battles
chosen
Battles are organized, often large-scale armed conflicts between opposing forces, characterized by strategic maneuvers, tactical engagements, and the pursuit of specific military objectives within a defined time and place.
-
E.
European war
A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:35 p.m.