Triple
T26883240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chernigov Governorate |
E676968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former subdivision of Ukraine |
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: former subdivision of Ukraine Context triple: [Chernigov Governorate, instanceOf, former subdivision of Ukraine]
-
A.
former raion of Ukraine
A former raion of Ukraine is an administrative district that existed as a second-level territorial unit within Ukraine’s regional structure but was later dissolved or reorganized, typically due to administrative reforms.
-
B.
historical region of Ukraine
A historical region of Ukraine is a geographically defined area within present-day Ukraine that is distinguished by its unique historical development, cultural heritage, and traditional boundaries formed over past centuries.
-
C.
former subdivision of the Kingdom of Poland
A former subdivision of the Kingdom of Poland is an historical administrative unit that once functioned as part of the kingdom’s territorial organization but no longer exists in its original form.
-
D.
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.
-
E.
raion of Ukraine
A raion of Ukraine is an administrative district within an oblast that serves as a second-level territorial unit for local governance and administration.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:40 a.m.