Triple
T15050451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russo-Persian conflicts |
E379344
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russo-Iranian wars |
C26479
|
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: Russo-Iranian wars Context triple: [Russo-Persian conflicts, instanceOf, Russo-Iranian wars]
-
A.
Russo-Persian War
chosen
The Russo-Persian War refers to any of several military conflicts between the Russian Empire and Persia (Iran), primarily in the 18th and 19th centuries, fought over territorial control and influence in the Caucasus and Caspian regions.
-
B.
Polish–Russian war
The Polish–Russian war refers to a series of historical military conflicts between Poland (or the Polish–Lithuanian Commonwealth) and Russia (including Muscovy and later the Russian Empire) over territorial control, political influence, and regional dominance in Eastern Europe.
-
C.
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.
-
D.
Ottoman–Habsburg wars
The Ottoman–Habsburg wars were a series of military conflicts from the 16th to the 18th centuries between the Ottoman Empire and the Habsburg Monarchy for dominance in Central and Southeastern Europe.
-
E.
battle of the Great Horde–Muscovy conflict
A battle of the Great Horde–Muscovy conflict is a military engagement between the Great Horde and the Grand Duchy of Muscovy, typically involving large-scale armed forces and shaping the political and territorial outcomes of their protracted struggle.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:01 a.m.