Triple
T8791352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Oblast (Russian SFSR) |
E209172
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | oblast of the Russian SFSR |
C25064
|
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: oblast of the Russian SFSR Context triple: [Western Oblast (Russian SFSR), instanceOf, oblast of the Russian SFSR]
-
A.
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.
-
B.
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).
-
C.
oblast of Ukraine
An oblast of Ukraine is a primary administrative division of the country, similar to a province or region, with its own local government and defined territorial boundaries.
-
D.
constituent republic of the Soviet Union
A constituent republic of the Soviet Union was a nominally sovereign national republic that, while having its own government and constitution, was politically and economically subordinate to the central Soviet federal authority.
-
E.
minority in the Soviet Union
A minority in the Soviet Union was an ethnic, national, religious, or cultural group that existed within the USSR’s multiethnic state structure but did not belong to the dominant Russian majority, often subject to specific policies of control, assimilation, or limited autonomy.
- F. None of above. chosen
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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:43 p.m.