Triple
T30123807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sloboda Cossack regiment |
E765632
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cossack military-administrative unit |
C52591
|
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 military-administrative unit Context triple: [Sloboda Cossack regiment, instanceOf, Cossack military-administrative unit]
-
A.
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.
-
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.
Loyalist cavalry unit
A Loyalist cavalry unit is a mounted military force composed of soldiers who remain steadfastly aligned with and fight on behalf of an established authority or ruling power during periods of conflict or rebellion.
-
D.
regional military unit
chosen
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.
component of Ottoman army
A component of the Ottoman army is a distinct organizational, functional, or tactical unit—such as infantry, cavalry, artillery, or auxiliary corps—that collectively contributed to the empire’s military structure and operations.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:13 p.m.