Triple
T4298163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ural Cossack forces |
E99767
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cossack host |
C10669
|
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: Cossack host Context triple: [Ural Cossack forces, instanceOf, Cossack host]
-
A.
Cossack
chosen
A Cossack is a member of a traditionally semi-military, self-governing community from the steppes of Eastern Europe, renowned for their horsemanship, warrior culture, and role in regional defense and expansion.
-
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 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.
-
D.
Mongol invasion of Europe battle
A Mongol invasion of Europe battle is a military engagement in which Mongol forces confront European armies during their 13th-century westward campaigns, characterized by highly mobile cavalry tactics, psychological warfare, and often decisive Mongol victories.
-
E.
King of Naples
The King of Naples is the sovereign ruler of the historical Kingdom of Naples, a monarchy that governed the southern part of the Italian Peninsula during various periods from the Middle Ages to the 19th 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:08 p.m.