Triple
T7512466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian State (Omsk Government) |
E177553
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | successor state claimant to the Russian Empire |
C11242
|
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: successor state claimant to the Russian Empire Context triple: [Russian State (Omsk Government), instanceOf, successor state claimant to the Russian Empire]
-
A.
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).
-
B.
tsar of Russia
The tsar of Russia was the autocratic monarch who ruled the Russian state and later empire, wielding supreme political, military, and religious authority until the monarchy’s abolition in 1917.
-
C.
Russian state
chosen
The Russian state is a centralized political entity that exercises sovereign authority over the territory and population of Russia through its institutions of governance, law, security, and administration.
-
D.
Grand Duke of Russia
A Grand Duke of Russia was a male member of the Russian imperial family, typically a son or grandson of a reigning emperor, who held high dynastic rank and status without necessarily exercising sovereign rule.
-
E.
oblast of Russia
An oblast of Russia is a primary administrative division comparable to a province, governed by regional authorities under the federal structure of the Russian Federation.
- 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_69c69f276b108190af2cc790b6554544 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:45 p.m.