Triple
T31475397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cossack host oblast |
E802978
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cossack territorial unit |
C25277
|
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 territorial unit Context triple: [Cossack host oblast, instanceOf, Cossack territorial unit]
-
A.
Cossack regiment
A Cossack regiment is a military unit composed of Cossack soldiers, traditionally organized for cavalry-based service within the armed forces of the Russian Empire and other Eastern European states.
-
B.
Cossack territory
chosen
Cossack territory is a semi-autonomous frontier region historically inhabited and governed by Cossack communities, characterized by military service, self-rule, and a distinct cultural identity within larger empires.
-
C.
Cossack
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.
-
D.
regional military unit
A regional military unit is an organized group of armed forces assigned to operate within a specific geographic area, responsible for defense, security, and military operations in that region.
-
E.
Cossack stanitsa
A Cossack stanitsa is a traditional self-governing Cossack village or settlement that served as both an administrative unit and a military community on the frontiers of the Russian Empire.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:28 p.m.