Triple
T28750709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ruin (period of Cossack Hetmanate civil wars) |
E731517
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | period of political instability |
C32211
|
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: period of political instability Context triple: [The Ruin (period of Cossack Hetmanate civil wars), instanceOf, period of political instability]
-
A.
period of warfare
A period of warfare is a span of time characterized by sustained armed conflict between organized groups, typically involving military operations, political objectives, and significant social and economic disruption.
-
B.
event in the Time of Troubles
An event in the Time of Troubles is a significant historical occurrence—such as a battle, political upheaval, famine, or succession crisis—that took place in Russia between 1598 and 1613 and contributed to the period’s instability and transformation.
-
C.
period of martial law
A period of martial law is a temporary state in which military authorities assume control over normal civilian government functions and legal processes, often in response to emergencies, unrest, or war.
-
D.
dynastic crisis
chosen
A dynastic crisis is a period of political instability triggered by disputed succession, extinction, or fragmentation of a ruling family’s line, often leading to conflict over legitimate authority.
-
E.
period of peace
A period of peace is a span of time during which societies or groups experience the absence of war and significant conflict, allowing for stability, recovery, and cooperative development.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 6:07 a.m.