Triple
T29635108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conquest of Astrakhan (1556) |
E755689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian military campaign |
C55992
|
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: Russian military campaign Context triple: [Conquest of Astrakhan (1556), instanceOf, Russian military campaign]
-
A.
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.
-
B.
Russo-Crimean War campaign
The Russo-Crimean War campaign is a strategic military operation or series of operations conducted by Russian forces in and around the Crimean region during the Crimean War, encompassing planning, logistics, battles, and political objectives.
-
C.
invasion of Russia
Invasion of Russia is a large-scale military campaign in which foreign forces attempt to penetrate, occupy, or subdue Russian territory, often facing vast distances, harsh climate, and strong defensive resistance.
-
D.
Eastern Front campaign
The Eastern Front campaign is a large-scale military operation or series of operations conducted on the eastern theater of war, typically involving prolonged, high-intensity ground combat across vast territories between major opposing powers.
-
E.
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.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
Created at: April 28, 2026, 6:43 p.m.