Triple
T8180415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cossack Host |
E191045
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cossack institution |
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 institution Context triple: [Cossack Host, instanceOf, Cossack institution]
-
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.
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.
-
C.
oblast of the Russian Empire
An oblast of the Russian Empire was an administrative-territorial unit, typically on the empire’s periphery, governed by appointed officials and possessing a lower status than a governorate (guberniya).
-
D.
Soviet administrative structure
The Soviet administrative structure was a highly centralized, hierarchical system of governance in which the Communist Party controlled state institutions, economic planning, and regional authorities through overlapping layers of bureaucratic and political oversight.
-
E.
Zemsky Sobor
Zemsky Sobor was a representative assembly in 16th–17th century Russia, convened by the tsar to consult nobles, clergy, and other estates on major state matters such as succession, legislation, and foreign policy.
- 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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:40 p.m.