Triple
T16496586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirny, Arkhangelsk Oblast |
E400698
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | town of oblast significance |
C22216
|
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: town of oblast significance Context triple: [Mirny, Arkhangelsk Oblast, instanceOf, town of oblast significance]
-
A.
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.
-
B.
autonomous oblast
An autonomous oblast is a type of administrative division within a country that possesses a degree of self-governance and cultural or political autonomy, typically established to recognize and accommodate a specific ethnic or regional group.
-
C.
town in Ukraine
A town in Ukraine is an urban locality with its own local government, infrastructure, and community, typically smaller than a city and situated within the administrative divisions of the country.
-
D.
municipal formation in Russia
chosen
A municipal formation in Russia is a legally defined local self-government entity, such as an urban or rural settlement, municipal district, or urban okrug, with its own elected bodies and administrative responsibilities within a specific territory.
-
E.
district of Belarus
A district of Belarus is an administrative subdivision within a Belarusian region (oblast), responsible for local governance, public services, and implementation of national policies in its territory.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:14 a.m.