Urban Entity Resolution
Address normalization candidates · Salmiya
Non-action commitment
Every output is presented to a named human reviewer and never reaches a downstream system on its own.
Review commitment
This system does not execute municipal action. It only prepares evidence-backed recommendations for authorized human review. Every decision creates an audit log entry.
Case summary
Multiple address variants surfaced for the same parcel. Reviewer approval needed for normalization.
Category
Address normalization
Recommended next step
Data steward reviews candidate group and accepts · rejects · defers.
Workflow steps
01
Match candidates
Surface candidate record groupings with confidence indicators and the fields that drove the grouping.
02
Reviewer decision
Reviewer accepts, rejects, or defers each grouping. No record is merged without explicit approval.
Decision Intelligence · KW-005
Projection only · no engine call
- What happened
- Multiple address variants surfaced for the same parcel. Reviewer approval needed for normalization.
- Why it surfaced
- Aged inspection request flagged by triage view; evidence packet partially complete; capture-date gap on 1 attachment(s).
- Evidence used
- ev-004
- Visual evidence used
- —
- Human review point
- Reviewer C · Data Steward (human review required)
- Audit proof
- —
- Operational value
- Reviewer reaches the case with full source-logged context and a recorded rationale, raising audit readiness for the district portfolio.
- Next step
- Data steward reviews candidate group and accepts · rejects · defers.
Linked evidence
1 items- Medium
ev-004 · municipal_registry
Address normalization candidates · Salmiya
Address variants for the same parcel surfaced for reviewer approval.
Captured: 2026-04-12
Reviewer decision
Every decision creates an audit entryCase audit trail
Full audit log →No audit entries yet.