Triple
T8623401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | administration of Domodedovo Urban Okrug |
E204222
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local executive authority |
C15097
|
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 executive authority Context triple: [administration of Domodedovo Urban Okrug, instanceOf, local executive authority]
-
A.
executive authority
Executive authority is the power and responsibility to implement, enforce, and administer laws and policies within a governing system or organization.
-
B.
system of local government
A system of local government is an organized framework of institutions, powers, and processes through which local authorities manage public services, enforce regulations, and represent community interests within a defined geographic area.
-
C.
local governmental entity
chosen
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.
-
D.
administrative authority
An administrative authority is an organization or body empowered by law or policy to implement, manage, and enforce rules, regulations, and public administration decisions within a defined jurisdiction.
-
E.
metropolitan authority
A metropolitan authority is a governing body responsible for planning, coordinating, and managing public services and development across a large urban area and its surrounding municipalities.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:26 p.m.