Triple
T1946664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accounts Chamber of Moscow |
E42069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | audit institution |
C3533
|
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: audit institution Context triple: [Accounts Chamber of Moscow, instanceOf, audit institution]
-
A.
auditing institution
chosen
An auditing institution is an independent organization responsible for systematically examining and evaluating financial records, operations, and controls to ensure accuracy, compliance, and accountability.
-
B.
independent administrative authority
An independent administrative authority is a public body, separate from the traditional executive hierarchy, endowed with regulatory or supervisory powers and functional autonomy to ensure impartial decision-making in a specific sector or policy area.
-
C.
financial oversight office
A financial oversight office is an organizational unit responsible for monitoring, reviewing, and ensuring the accuracy, compliance, and integrity of an entity’s financial activities and reporting.
-
D.
official institution
An official institution is a formally established organization, typically created or sanctioned by a government or authoritative body, that exercises recognized powers and responsibilities within a defined legal or social framework.
-
E.
office of inspector general
The Office of Inspector General is an independent oversight body within an organization or government agency responsible for auditing, investigating, and evaluating programs and operations to prevent fraud, waste, abuse, and misconduct.
- 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.