Triple
T33256412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitutional Council of Kazakhstan |
E851387
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state body of Kazakhstan |
C59228
|
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: state body of Kazakhstan Context triple: [Constitutional Council of Kazakhstan, instanceOf, state body 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.
economic region of Kazakhstan
An economic region of Kazakhstan is a territorially defined area within the country grouped by shared economic characteristics, resources, and development priorities to facilitate regional planning and management.
-
D.
executive body of Kazakhstan
chosen
The executive body of Kazakhstan is the branch of government responsible for implementing laws, managing state administration, and directing national policy under the leadership of the President and the Government (Cabinet of Ministers).
-
E.
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.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:31 a.m.