Triple
T32580339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sich fortress |
E832764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Zaporizhian Cossack stronghold |
C54018
|
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: Zaporizhian Cossack stronghold Context triple: [Sich fortress, instanceOf, Zaporizhian Cossack stronghold]
-
A.
Cossack stanitsa
chosen
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.
-
B.
Khazar stronghold
A Khazar stronghold is a fortified military and administrative center of the Khazar Khaganate, typically featuring defensive walls, garrisons, and facilities for governance and trade control.
-
C.
Cossack territory
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.
-
D.
Cossack communal assembly
A Cossack communal assembly is a self-governing gathering of Cossack community members that collectively deliberates and decides on political, military, and social matters.
-
E.
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.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:04 a.m.