The identity layer beneath Context
Every record is partial.
The graph is continuous.
The Commonplace Graph resolves fragments from agency, public, commercial, partner, and open sources into persistent entities and relationships.
See how resolution works ↓Entity resolution
From isolated record
to durable identity.
Probbl does not require one source to know the whole person. It looks for agreement across many incomplete observations.
01▤
Ingest
Preserve each source record with its native provenance, confidence, and contractual restrictions.
Name variantsPhones & emailsGovernment IDsDevice ad IDsPlate readsAccount handles02⌁
Normalize
Convert inconsistent records into comparable observations without discarding the original.
Address historyPhone reuseDevice clusteringTimestamp repairAlias expansionGeo confidence03◎
Resolve
Score whether records describe the same person, place, vehicle, device, or organization.
Shared nighttime locationCo-travel sequenceHousehold proxyTransactional overlapContact recoveryRecurring proximity04⌘
Connect
Create weighted relationships that can be searched, monitored, and inherited by downstream signals.
DirectHouseholdCommercialCo-presenceSecond-degreeBehavioral affinityRelationship intelligence
A relationship is more than a line.
Each edge in the Commonplace Graph carries a type, confidence, time range, evidence history, and relevance state.
- PersistentEdges survive the source record that first created them.
- DirectionalOne person’s relevance may affect another differently.
- TemporalCurrent, recurring, and historical connections remain distinguishable.
A relationship may exist before either party becomes the named subject of an inquiry.
Edge inspector3 relationships
ABAvery Bell
91%probable household
JLJordan Lee
Shared residence182 overnight observationsShared vehicle46 recurring associationsAccount relationship2 commercial records
First inferred Mar 8, 2024 · Last reinforced Sep 6, 2026
ABAvery Bell
78%recurring contact
MCMorgan Chen
Device co-presence23 observationsCommon destination4 recurring locationsShared account2 retail profiles
No agency contact record directly connects these entities.
ABAvery Bell
63%through Jordan Lee
RWRiley West
Graph pathAvery → Jordan → RileyAgency relevanceActive watch attached to RileyDirect evidenceNone observed
Operational relevance is inherited from a connected entity.
Source fabric
No single source
has to be complete.
Probbl combines records collected for different purposes, under different standards, into a common information model.
AAgency systems
Records already held by the customer or participating agencies.
+
Agency systems
Records already held by the customer or participating agencies.
RMS · CAD · citations · jail · field interviews · calls for service
Agency records are treated as authoritative within their originating jurisdiction, even when the underlying narrative is disputed or later amended.
PPublic records
Government-published and legally accessible records.
+
Public records
Government-published and legally accessible records.
Property · courts · corporations · licenses · campaign filings
Probbl preserves historical records after they disappear from the current public interface when licensing and agency policy allow.
CCommercial insights
Licensed identity, mobility, household, and transaction-derived datasets.
+
Commercial insights
Licensed identity, mobility, household, and transaction-derived datasets.
Consumer identity · device segments · retail profiles · risk attributes
Commercial records may have been collected without the person knowing they would later be used in a public-safety context.
OOpen sources
Publicly observable web content and structured metadata.
+
Open sources
Publicly observable web content and structured metadata.
Social profiles · business pages · public images · archived content
Deletion at the original source does not automatically remove derived relationships already incorporated into the graph.
Historical continuity
Context does not disappear when attention moves on.
Source records, derived entities, and relationship histories follow separate retention policies. Customers can configure visibility by role while preserving the record required for audit, model evaluation, and future resolution.
Source observationContract or source policy
Resolved identityLife of account + configured archive
Derived relationship5 years after last reinforcement
Signal historyImmutable audit retention
Illustrative defaults. Agency policy and applicable law may require different periods.See the graph in use
Open Avery Bell record →