What is already in the database

The database covers 14 editorial categories, from exile opposition and protest figures to politicians, media, NGOs, lawyers, speakers, social media, eco-activists, and religious organizations. Each profile combines core facts, event chronology, related entities, and a route back to source material.

How to use it

  • Start with search or the index when you need a specific person or organization.
  • Open the relationship graph and timeline to see context, roles, and event sequence quickly.
  • Use related profiles and sources inside each dossier as the path for deeper verification.

Database coverage

Metrics are calculated from the published corpus and do not replace verification of individual statements.

Published dossiers
305
Canonical sources
759
RU coverage
100%
KZ coverage
100%
EN coverage
100%
Dossiers with chapters
100%
Event source coverage
14%
Relationship source coverage
1%
Corpus readiness
62%
Evidence integrity
54%

Russian is the primary editorial version. Other languages are published after editorial review, without machine-filled content.

Corpus enrichment queue

These workstreams are generated from live quality metrics. They show what is already connected to the database and what still needs editorial review.

P0

Key relationship review

Relationships appear in the graph only after source linkage and editorial review; archival cross-references stay in the queue.

Next actionExport the highest-traffic relationship queue and attach source-backed approve/reject decisions.

Links
6 556
Evidence
121
Readiness
1%
P0

Immutable source snapshots

Public URLs can change, so priority sources need snapshots or hashes.

Next actionMaterialize snapshots for cited sources that are already public and technically fetchable.

Snapshots
759
Sources
759
Coverage
100%
P1

Reviewable statement layer

Draft facts are already structured, but the public statement layer opens only after review.

Next actionSelect priority draft statements, add qualifiers and publish only reviewed source-backed facts.

Drafts
687
Published
687
With evidence
687
P2

Monitoring dates and clusters

Mentions become useful when publication date, source, duplicate cluster and match quality are visible.

Next actionBackfill lawful publication dates, cluster reposts and surface source/date confidence.

Approved
1 240
Dated
635
Undated
605
P2

QazGeo location review

Maps should expose accepted, reproducible locations rather than raw extraction candidates.

Next actionReview featured-profile candidates first and persist only accepted QazGeo locations.

Locations
31
Candidates
0
Reviewed
5
P3

Documents and text blocks

Primary documents should be segmented into citable blocks and linked back to profiles.

Next actionAdd OCR/page blocks and attach entity anchors only where document text supports the match.

Documents
2
Published
1
Blocks
49

Data quality queue

This public view turns abstract quality warnings into concrete groups of dossiers, sources, and documents awaiting editorial or technical work.

4 active groups 797 open items
P1

Dossiers without event chronology

Chronology is required for sequence checks, date filters, and analytical collections.

Next actionAdd dated timeline events from cited sections or primary sources.

open items
114
samples
6
P1

Dossiers without images

Images improve profile recognition, but must carry source, alt text, and rights metadata.

Next actionAttach rights-cleared images with source, caption and alt text.

open items
77
samples
6
P2

Mentions without publication dates

Dates are required for filters, timelines, deduplication, and monitoring freshness.

Next actionBackfill publication dates from lawful source metadata and keep uncertain matches pending.

open items
605
samples
6
P3

Documents without precise profile anchors

Documents become more useful when a profile links to a specific text block rather than the whole file.

Next actionLink documents to exact text blocks only when aliases or source text support the anchor.

open items
1
samples
1

Public API and contract assets

Public contexts, contract material and citation rules are exposed through the AI index, sitemap and data-quality surface.

Runtime status

The public summary shows which working contours are connected to the published database right now.

Version
2.5.0
Database
ok
QazStack
1.37.0 · 11 primitives
QazGeo
connected
QazCompute
SyncComputeClient
Monitoring
2026-08-17 19:25

How to read evidence labels

A label applies to a specific chapter, event, or relationship. It describes evidence state, not an overall judgement of a person.

Verified source

A direct link points to a reviewed primary source or a reliable secondary source.

Source not yet editorially reviewed

A direct source link is attached, but editorial content review has not yet been recorded.

Not line-reviewed

The material was migrated from the Qazpolit archive and retains a link to the original publication.

Compiled material

The text was structured from the editorial corpus, but sources have not yet been mapped to individual statements.

Source pending

No direct link is attached yet; the fragment should not be treated as source-level verified.

Publishing principles

The corpus combines open sources with material migrated from the Qazpolit archive. Every block shows its evidence state, and a missing direct source link remains visible. The platform does not rate the people or organizations it describes; the material is presented for reference.

  • The project shows links, dates, statuses, and sources, but it does not replace investigation or legal assessment.
  • If evidence is missing, the block stays hidden or intentionally incomplete.
  • Priority goes to verifiable open sources and to structuring existing material, not decorative copy.