Entity resolution

Candidate portfolios are research sets

How normalized names and addresses create useful leads without claiming a confirmed holdings list.

Updated
2026-08-04
Read time
2 min
Editorial state
Methodology reviewed
Author
Acren Research
Reviewer
Methodology review team
On this page
  1. Normalize before you connect
  2. Supporting and conflicting evidence
  3. What to leave for the reviewer
Direct answer

A candidate portfolio is a set of properties connected by supporting name, address or registration observations. It is a research set for review, not a confirmed holdings list or beneficial-ownership conclusion.

Normalize before you connect

Acren compares normalized names, filing jurisdictions, registration identifiers and addresses across source classes. Each agreeing observation can support a candidate edge between a property, an owner string and an entity registration.

The edge remains a candidate when the evidence could describe a shared agent, an old address, a common name or an unrelated filing. Confidence is a review aid, not a fact about control.

Relationship evidenceCandidate · not confirmed
Normalized name
RIVERSIDE COMMERCE LLC
Jurisdiction
Texas
Registration
LLC-0994412 · Active
Registered address
Dallas, TX

Supporting observations

  • Normalized name match: RIVERSIDE COMMERCE LLC ≈ Riverside Commerce, LLC
  • Registered-agent address agreement across two filings
  • Mailing address on assessment roll matches entity principal office

Conflicting or missing

  • Two active registrations share the normalized name in different states
  • Officer/manager names are not published by this jurisdiction

The relationship stays labeled a candidate until a reviewer promotes it. Acren does not assert beneficial ownership.

Synthetic product demonstration. It shows a research pattern, not a live record or completeness claim.

Supporting and conflicting evidence

  • Supporting: normalized name agreement across the property and entity records.
  • Supporting: registered or principal address agreement across filings.
  • Conflicting: multiple active registrations share a normalized name.
  • Missing: officers, managers or control information are not published.

What to leave for the reviewer

FieldValue / stateReading
Normalized nameComparison keyDerived from observed strings
JurisdictionFiling state or authorityObserved
RegistrationNumber and statusObserved where published
ConfidenceReview priorityNot a control claim
Continue research

See the provenance of a relationship.