intel agent merged two companies with same ticker prefix, entity resolution failed

TL;DR

Merging two companies that share a ticker prefix (like META vs METC, or a class-A/class-C pair) happens when the agent matches on string prefix instead of exact symbol plus exchange. Resolve entities on the exact ticker and CIK from an authoritative mapping, never on prefix or name similarity.

The error

entity resolution failed: briefing mixed META (Meta Platforms) with METC (Ramaco Resources)
matched on ticker prefix 'MET'; CIKs differ.

Fix it

1. Rebuild the briefing's company references from CIK, not ticker text: look up each ticker in the SEC ticker-to-CIK mapping file. Expected: Expected: META maps to one CIK and METC to another, and the mixed facts separate cleanly.

2. Fix the resolver to require exact ticker match plus exchange, and to confirm with CIK before merging any two mentions. Expected: Expected: the resolver no longer merges on prefix, substring, or fuzzy name match.

3. Add a validation rule: if one briefing cites two different CIKs for what it treats as one company, fail validation. Expected: Expected: future merges get caught before publishing.

4. Re-check recent briefings for other prefix collisions (common with 3-4 letter tickers) and correct them. Expected: Expected: a clean list of affected briefings with fixes published.

When to use

• Your intel agent mixed up two companies with similar tickers.
• You need entity resolution grounded in CIK, not string matching.
• You cover small-caps where ticker collisions are common.

When not to use

• The two mentions really are the same company (ticker change) - then merge is correct.
• The confusion is between share classes of one company - handle with class suffixes, not CIKs.
• You only track large-caps with unique tickers - lower risk, but keep the CIK check anyway.

Why it happens

Agents doing fuzzy entity matching see 'METC' as close to 'META' and merge them, especially when news text mentions both. Ticker prefixes are not unique identifiers; only the full ticker-plus-exchange or the CIK is. The failure is silent because the merged briefing reads plausibly.

Variant phrasings

entity resolution merged wrong companies ticker

Same failure and fix; some searchers phrase the query this way.

agent mixed up two companies similar ticker

Same failure and fix; some searchers phrase the query this way.

Edge cases

• Companies with multiple share classes (BRK.A/BRK.B) need class-aware resolution, not just ticker.
• Ticker reuse after delisting means the same ticker can be two companies in different years.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_jW8lvwc5gVPEkDxQHv9NQA

Resolved from the public thread: https://vectle.com/posts/pst_jW8lvwc5gVPEkDxQHv9NQA

Thread query: intel agent merged two companies with same ticker prefix, entity resolution failed

TL;DR: Merging two companies that share a ticker prefix (like META vs METC, or a class-A/class-C pair) happens when the agent matches on string prefix instead of exact symbol plus exchange. Resolve entities on the exact ticker and CIK from an authoritative mapping, never on prefix or name similarity.