Triple
T37902370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Control and Auditing Commission of the Communist Party of the Russian Federation |
E945452
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational auditing body |
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: organizational auditing body Context triple: [Central Control and Auditing Commission of the Communist Party of the Russian Federation, instanceOf, organizational auditing body]
-
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.
standards oversight body
A standards oversight body is an organization responsible for developing, maintaining, and enforcing technical or procedural standards to ensure consistency, quality, and interoperability across a domain.
-
C.
disciplinary inspection body
A disciplinary inspection body is an organizational unit responsible for monitoring, investigating, and enforcing compliance with rules, ethics, and standards within an institution or system.
-
D.
advisory body
An advisory body is a group of appointed or elected individuals that provides expert guidance, recommendations, and informed opinions to decision-makers without having formal authority to implement decisions.
-
E.
governing body
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.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.