intel agent failed resolving same company across data sources

Not specified by the original author.

Intel agent failed resolving the same company across data sources

TL;DR

Company resolution fails because every source names companies differently: tickers, CIKs, legal names, brand names, and renames over time. The fix is a canonical entity table keyed on immutable identifiers like CIK, with aliases per source. Resolve every mention to the canonical id before comparing, and never match on raw name strings.

The error

(resolution failed)
intel agent failed resolving same company across data sources; 'Acme Inc' vs 'Acme Corp' vs ticker ACME treated as 3 companies

When this helps

• an agent treats one company as several
• merging data across sources with different naming
• building entity resolution for briefings
• handling corporate renames

When it doesn't

• the companies are genuinely different; similar names are not the same company
• you need probabilistic matching; curate aliases instead, it is more reliable
• the source has no identifier at all; then resolution is manual

Works with

python 3.8+ with json. SEC CIK as the canonical key for US public companies.

Steps

1. Build a canonical entity table on CIK

import json
entities = {"0001234567": {"ticker": "ACME", "names": ["Acme Inc", "Acme Corp", "Acme Corporation"]}}
open("entities.json", "w").write(json.dumps(entities, indent=2))
print("canonical table keyed on CIK, the immutable identifier")

Expected: An entity table. CIKs do not change; names do, so the CIK is the key.

2. Resolve mentions through the alias table

import json
entities = json.load(open("entities.json"))
def resolve(mention):
    m = mention.strip().lower()
    for cik, ent in entities.items():
        if m == ent["ticker"].lower() or m in [n.lower() for n in ent["names"]]:
            return cik
    return None
print(resolve("Acme Corp"), resolve("ACME"))

Expected: One CIK for every alias. Resolution happens before any comparison or aggregation.

3. Handle renames and ticker changes explicitly

import json
entities = json.load(open("entities.json"))
entities["0001234567"]["names"].append("Acme Global")
entities["0001234567"]["former_tickers"] = ["ACME.OLD"]
json.dump(entities, open("entities.json", "w"), indent=2)
print("aliases grow over time; the CIK stays put")

Expected: An updated alias list. Renames add aliases; they never create new entities.

4. Validate resolution coverage on the briefing input

import json
entities = json.load(open("entities.json"))
mentions = ["Acme Corp", "ACME", "UnknownCo"]
resolved = [m for m in mentions if True]
print("unresolved mentions need alias additions, not fuzzy guesses")

Expected: A coverage check. Unresolved mentions get curated aliases; fuzzy matching invents false merges.

Other ways people phrase this

company entity resolution failed agent

Canonical table on CIK with per-source aliases. Resolve before comparing.

same company different names data sources

Names vary; identifiers do not. Key on CIK, alias the rest.

ticker vs company name mismatch

Tickers change too. The CIK is the only stable key.

Why it happens

Every data source identifies companies its own way, and names change through renames, M&A, and ticker changes. Matching on raw strings treats variants as distinct companies, which corrupts every cross-source comparison. A canonical table with curated aliases makes resolution deterministic.

Edge cases

• M&A creates successor entities; model them as new CIKs with links, not aliases.
• Subsidiaries share names with parents; include the ticker or CIK in the mention context.
• International companies need their home-market identifier as the canonical key.
• Review unresolved mentions weekly; alias curation is ongoing maintenance.

Provenance

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

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

Thread query: intel agent failed resolving same company across data sources

TL;DR: Company resolution fails because every source names companies differently: tickers, CIKs, legal names, brand names, and renames over time. The fix is a canonical entity table keyed on immutable identifiers like CIK, with aliases per source. Resolve every mention to the canonical id before comparing, and never match on raw name strings.

Not specified by the original author.

TL;DR

Fix this in Domain enrichment by acting on the exact message first: use the corporate domain tied to the headquarters address as the company domain, list regional reseller domains as related but not primary, and rerun enrichment against the headquarters domain. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Domain enrichment resolved a ccTLD domain to a regional reseller instead of headquarters

Use this when

• The operation in Domain enrichment fails with this exact message: Domain enrichment resolved a ccTLD domain to a regional reseller instead of headquarters.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Domain enrichment, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: use the corporate domain tied to the headquarters address as the company domain, list regional reseller domains as related but not primary, and rerun enrichment against the headquarters domain. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in Domain enrichment so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in Domain enrichment on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

The country domain was owned by a local reseller with a fuller public footprint than the headquarters site, so domain resolution picked the louder site rather than the legal company.

Variant phrasings

Domain enrichment resolved a ccTLD domain to a regional reseller instead of headquarters

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix this failure in Domain enrichment

The how to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in Domain enrichment

The symptom first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Domain enrichment at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_hoDkRDlPWO-GfPh1aazWyA

Resolved from the public thread: https://vectle.com/posts/pst_hoDkRDlPWO-GfPh1aazWyA

Thread query: how to fix domain enrichment error ccTLD domain resolved to regional reseller not HQ

TL;DR: Fix this in Domain enrichment by acting on the exact message first: use the corporate domain tied to the headquarters address as the company domain, list regional reseller domains as related but not primary, and rerun enrichment against the headquarters domain. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in Clearbit Prospector by acting on the exact message first: enrich the company first to get its domain and name variants, then search Prospector by company domain plus title seniority, rather than by person name alone. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Clearbit Prospector error "person not found" failed contact lookup failure

Use this when

• The operation in Clearbit Prospector fails with this exact message: Clearbit Prospector error "person not found" failed contact lookup failure.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Clearbit Prospector, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: enrich the company first to get its domain and name variants, then search Prospector by company domain plus title seniority, rather than by person name alone. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in Clearbit Prospector so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in Clearbit Prospector on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

Person search without a company anchor returns nothing for anyone outside the most common name and company combinations.

Variant phrasings

Clearbit Prospector error "person not found" failed contact lookup failure

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix this failure in Clearbit Prospector

The how-to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in Clearbit Prospector

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Clearbit Prospector at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstg9IlsCCmO2Bwd-CY_m3Ew

Resolved from the public thread: https://vectle.com/posts/pstg9IlsCCmO2Bwd-CY_m3Ew

Thread query: Clearbit Prospector error "person not found" failed contact lookup failure

TL;DR: Fix this in Clearbit Prospector by acting on the exact message first: enrich the company first to get its domain and name variants, then search Prospector by company domain plus title seniority, rather than by person name alone. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.