Triple
T3850324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Moscow Oblast |
E85279
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional executive authority |
C416
|
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: regional executive authority Context triple: [Government of Moscow Oblast, instanceOf, regional executive authority]
-
A.
executive authority
chosen
Executive authority is the power and responsibility to implement, enforce, and administer laws and policies within a governing system or organization.
-
B.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
C.
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.
-
D.
directly elected regional authority
A directly elected regional authority is a governing body at the subnational level whose members are chosen by popular vote to administer and make policy decisions for a specific geographic region.
-
E.
regional directors
Regional directors are senior managers responsible for overseeing operations, strategy implementation, and performance across multiple locations within a defined geographic area.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.