Triple
T8669182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Krai |
E205752
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of the Russian Empire |
C24568
|
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: region of the Russian Empire Context triple: [Western Krai, instanceOf, region of the Russian Empire]
-
A.
former subdivision of the Russian Empire
chosen
A former subdivision of the Russian Empire is an obsolete administrative-territorial unit that once functioned as part of the empire’s governmental structure but no longer exists in its original form.
-
B.
economic region of Russia
An economic region of Russia is a territorial grouping of federal subjects organized for coordinated economic planning, development, and statistical analysis based on shared geographic, industrial, and infrastructural characteristics.
-
C.
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).
-
D.
district of Russia
A district of Russia is an administrative subdivision within a federal subject that manages local governance, public services, and regional implementation of national laws for its constituent settlements.
-
E.
state institution of the Russian Empire
A state institution of the Russian Empire was an official governmental body or administrative organ responsible for implementing imperial policies, managing public affairs, and exercising authority within the empire’s centralized bureaucratic system.
- 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:31 p.m.