Triple
T32776747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherkassk |
E838228
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former Cossack capital |
C1296
|
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: former Cossack capital Context triple: [Cherkassk, instanceOf, former Cossack capital]
-
A.
urban center of Kyivan Rus
An urban center of Kyivan Rus was a fortified political, economic, and religious hub that concentrated princely authority, trade networks, artisan production, and ecclesiastical institutions within a densely settled town or city.
-
B.
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.
-
C.
former capital city
chosen
A former capital city is an urban center that once served as the official seat of government and administrative authority for a country or region but no longer holds that status.
-
D.
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.
-
E.
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.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:13 a.m.