Triple
T17099404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimean campaigns of 1687 and 1689 |
E414939
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russo-Crimean War campaign |
C38829
|
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-Crimean War campaign Context triple: [Crimean campaigns of 1687 and 1689, instanceOf, Russo-Crimean War campaign]
-
A.
Russo-Persian War
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.
Soviet campaign
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.
-
C.
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.
-
D.
Roman–Pontic war
The Roman–Pontic war was a series of military conflicts between the Roman Republic and the Kingdom of Pontus, primarily under King Mithridates VI, over control of Asia Minor and the eastern Mediterranean in the 1st century BCE.
-
E.
land offensive
A land offensive is a coordinated, large-scale military operation conducted primarily by ground forces to seize territory, defeat enemy formations, or achieve strategic objectives on land.
- F. None of above. chosen
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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:35 a.m.