Skip to content

How accurate is this?

Every number here is measured, recomputed on request, and explained. If something looks wrong, the record's source link is the fastest check, and the contact address at the bottom is the second.

269records published
379held back by the rules
28folded into another record
81%placed on a hundred-block

Data reliability

Checks failing

Each night an automated audit reconciles published totals and checks the source-to-record chain, source health, official revision dates, the active extraction evaluation, and the latest stored snapshot from each source. A failed check stays visible here and makes the deep system health check fail; no person can mark it passed.

Last run Nov 5, 2026.

Automated checkStatusObservedExpected
published provenance
Published incidents with an incomplete source, snapshot, extraction, prompt, model, score, or publication chain.
pass00
council provenance
Published council actions with an incomplete source, snapshot, extraction, prompt, or model chain.
pass00
official provenance
Official statistics with an incomplete source-item or snapshot chain.
pass00
snapshot integrity
Latest stored source snapshots missing from private storage or not matching their recorded SHA-256 digest.
pass0/70 failed latest-source snapshots
extraction backlog
Enabled-source items still fetched or extracting after the processing window.
pass00 older than 6 hours
source health
Enabled ingestion sources marked degraded or failing.
pass00
official revision dates
Official values missing a revision key, date basis, or an available publisher report date.
pass00
official content horizon
Official datasets with stored values whose latest period is older than their source-specific publication allowance.
pass3/3 within horizonlatest stored period within the configured horizon for every official dataset
rollup total
The city-month all-type rollups must reconcile to the published incident population.
pass269/269rollup total equals published incidents
eval current
The latest police extraction evaluation must describe the active prompt and model.
failextract-police-v4 / gpt-5-miniextract-police-v4 / gpt-5-mini, run within 35 days
eval precision
Incident-detection precision on the labelled police fixture set.
fail0.8108108108108109>= 0.9
eval recall
Incident-detection recall on the labelled police fixture set.
fail0.7792207792207793>= 0.8
eval pii
Labelled identifier matches that escaped both automated privacy checks.
fail20

Extraction accuracy

93 real police releases, hand-labelled, run through the live model (gpt-5-mini, prompt extract-police-v4) on Sep 10, 2026. Detection is whether the model found the same incidents a person did; field accuracy is whether each detail matched.

81%precision
78%recall
79%F1
2identifier matches that escaped privacy checks
2raw identifier matches caught
FieldAccuracy on matched incidents
type92%
occurred on95%
occurred precision100%
street100%
block100%
area100%
target kind80%
stage98%
charges80%
outcome100%
estimated damage cad98%
is follow up88%

Against the Police Services Board

The Board's monthly reports count every incident the police recorded. We count only incidents that appeared in a public release. The gap is the point: this is a record of what was made public, calibrated against the official total, not a substitute for it. Twelve months to 2025-07, the latest the Board has reported; Board figures on file for 12 of those months.

Category (Board metric)On the ledgerBoard totalShare
Mischief / vandalism to property (property.mischief)04510.0%
Break and enter — business (property.break_enter_business)01010.0%
Break and enter — other (property.break_enter_residence)12830.4%
Theft under $5,000 (incl. shoplifting) (property.theft)11,7620.1%
Theft from motor vehicle (property.theft_from_motor_vehicle)03550.0%
Assault (public setting) (violence.assault)67820.8%
Robbery (violence.robbery)1631.6%

What the rules did

No person reviews or edits a record's content; deterministic rules publish or discard, and "held back" means discarded. The operator can remove a record or send it back through the rules, and every such action is logged. Every rule that fires is logged with what it did. The rules.

RuleResultRecords
Privacy check fired (free-text detail removed)published222
Street not matched (published without a block)published76
Date implausible (publication date used)published30
Model confidence below the flag thresholdpublished28
Privacy check fired (free-text detail removed)held back7
Unusual number of incidents in one releasepublished6
Model confidence below the flag thresholdheld back3

Sources

SourceStatusLast read
Sault Ste. Marie Police Service — media releasesokNov 6, 2026
Wayback Machine — historical saultpolice.ca releasesok—
SSM Police Services Board — monthly reports (PDF)okNov 5, 2026
City of Sault Ste. Marie — council (eSCRIBE portal)okNov 5, 2026
Ontario Court of Justice — courthouse-level criminal statisticsokOct 14, 2026
StatCan 35-10-0180-01 — incident-based crime, SSM Police ServiceokOct 14, 2026
SIU news releases (filtered to SSM)okSep 8, 2026
SooToday — City Police Beatoff—

Partner feeds

Active-feed participation is withheld until three organisations participate. A block shows partner rows only once three partners have rows there; rows below that threshold are not counted publicly. The partner program.

No partner rows yet.

Corrections

Corrections and takedowns to date: 1. Report a wrong record or privacy concern. Privacy concerns alert the operator immediately; removals are logged and reach licensees through the corrections feed. We answer within five Ontario business days.

Names are never published, so a correction concerns the record's facts, not a person. A record's source link points to the source's own publication; what that document says is theirs to correct.