Triple
T32893518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zalesye |
E841402
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical region of Russia |
C61580
|
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: historical region of Russia Context triple: [Zalesye, instanceOf, historical region of Russia]
-
A.
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.
-
B.
former subdivision of the Russian Empire
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.
-
C.
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.
-
D.
federal territory of Russia
A federal territory of Russia is a special type of federal subject directly administered by the federal government, typically encompassing strategically important or unique areas with a distinct governance regime separate from surrounding regions.
-
E.
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.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:18 a.m.