Triple
T1946666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accounts Chamber of Moscow |
E42069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal financial control authority |
C825
|
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: municipal financial control authority Context triple: [Accounts Chamber of Moscow, instanceOf, municipal financial control authority]
-
A.
municipal agency
chosen
A municipal agency is a local government organization responsible for delivering specific public services, enforcing local regulations, and managing community programs within a city or town.
-
B.
municipal government committee
A municipal government committee is a formally organized group within a local government tasked with studying specific issues, advising the city or town council, and sometimes making decisions or recommendations on policies, services, and regulations affecting the community.
-
C.
municipality
A municipality is a local administrative unit, such as a city, town, or district, governed by elected officials and responsible for providing public services and regulations within its defined geographic area.
-
D.
municipal enabling act
A municipal enabling act is a statute passed by a higher level of government that grants municipalities the legal authority and powers necessary to govern and regulate local affairs.
-
E.
municipal advisory committee
A municipal advisory committee is a formally appointed group of community members that provides recommendations and expert input to local government officials on specific policy areas, projects, or issues.
- 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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:36 p.m.