Triple
T21509195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dedoplistsqaro Municipal Council |
E530671
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local self-government representative body |
C172
|
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: local self-government representative body Context triple: [Dedoplistsqaro Municipal Council, instanceOf, local self-government representative body]
-
A.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
B.
regional electoral body
A regional electoral body is an organization responsible for administering, supervising, and ensuring the integrity of elections within a specific subnational geographic area.
-
C.
local organ of state power
A local organ of state power is a governmental body operating at the subnational level that exercises state authority and administers public affairs within a defined local territory in accordance with national law.
-
D.
local governmental entity
A local governmental entity is an administrative organization, such as a city, county, or district, that exercises governmental authority and provides public services within a specific geographic area below the level of the central or national government.
-
E.
proposed governmental body
A proposed governmental body is a conceptual organization suggested to perform specific public functions or governance roles, but which has not yet been formally established or granted legal authority.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:25 p.m.