Triple
T9860472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orenburg Cossack settlements |
E239696
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cossack settlements |
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 settlements Context triple: [Orenburg Cossack settlements, instanceOf, Cossack settlements]
-
A.
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.
-
B.
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.
-
C.
fortified settlement
A fortified settlement is a community enclosed by defensive structures such as walls, ramparts, or palisades, designed to protect its inhabitants and resources from external threats.
-
D.
Sauk settlement
A Sauk settlement is a community or village established and inhabited by the Sauk (Sac) people, typically organized around kinship networks, seasonal subsistence activities, and cultural practices in their traditional homelands.
-
E.
Russian-style colony
A Russian-style colony is a settlement or territory established and controlled by Russia that reflects Russian governance, culture, language, and economic interests, often emphasizing centralized authority and strategic or resource-based exploitation.
- 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_69ca84e6493081909cf58c8d42ea856b |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:35 p.m.