Triple
T34479878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Kazakhstan economic region |
E885153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | economic region of Kazakhstan |
C60721
|
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: economic region of Kazakhstan Context triple: [Western Kazakhstan economic region, instanceOf, economic region of Kazakhstan]
-
A.
region of Kazakhstan
A region of Kazakhstan is a primary administrative division of the country, governed by a regional authority and encompassing multiple districts, cities, and rural settlements within a defined geographic area.
-
B.
district of Kazakhstan
A district of Kazakhstan is an administrative subdivision within a region (oblys) that governs local municipalities, manages public services, and implements regional and national policies at the local level.
-
C.
region of Turkmenistan
A region of Turkmenistan is a primary administrative division of the country, encompassing a defined geographic area with its own local governance, population, and economic activities under the national government.
-
D.
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.
-
E.
economic region of Azerbaijan
An economic region of Azerbaijan is a territorially defined area within the country grouped by shared economic characteristics, resources, and development priorities to facilitate regional planning and management.
- 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.