.svg){kind=icon}
Learn
Master data management builds one governed golden record for cooperative, owned commercial data; entity resolution links records across many structured and unstructured multi-source systems into one provenance-preserving entity for analyst review.
Last updated: October 18, 2026
Why it matters to your mission. A program team told that it already owns a master data management capability often assumes the hard part of connecting fragmented data is solved, then discovers that the mission data is adversarial, multi-source, and classified in ways the commercial tool never expected. Master data management builds one governed golden record for cooperative, owned data; entity resolution links records across many structured and unstructured systems into one provenance-preserving entity without overwriting the sources. The outcome is a briefable, defensible picture the originals still support, not a merged record no analyst can trace back.
Master data management builds one governed golden record for cooperative, owned commercial data; entity resolution links records across many structured and unstructured multi-source systems into one provenance-preserving entity for analyst review. Master data management, usually shortened to MDM, is a governance discipline for an organization's own reference data; entity resolution is the matching capability that decides which records describe the same real-world entity, and it is one engine MDM depends on.
Put plainly: MDM asks "what is the one authoritative record for this customer, product, or vendor?" Entity resolution asks "across every system we hold, structured and unstructured, which records are the same entity, how confident are we, and what traces back to each source?" The two overlap on matching and diverge on almost everything else.
No. They are related, and they get confused because both end up deciding whether two records describe the same thing, but they solve different problems.
Master data management is a program for governing an enterprise's core reference data: customers, products, suppliers, locations. Its deliverable is a golden record, a single curated version of the truth that downstream systems read from, maintained through stewardship workflows, data quality rules, and governance policy. MDM assumes the data is yours, reasonably cooperative, and worth collapsing into one authoritative row.
Entity resolution is the narrower, sharper capability of deciding which records across sources refer to the same real-world entity. It extracts entities from free text, generates candidate matches at scale, scores them, clusters the records that belong together, attaches a confidence value, routes ambiguous cases to a person, and persists the result with a trace back to every contributing source. MDM uses entity resolution to decide what to merge; entity resolution does not require MDM to be useful.
Hold them apart this way: master data management is the governance program that decides an organization should have one authoritative record and maintains it; entity resolution is the matching engine that figures out which records are the same entity in the first place.
The split becomes obvious the moment the data stops being clean, owned, and cooperative. MDM was built for a friendly problem: an enterprise's own customer and product data, where the subject has no reason to hide, the fields are defined, and the goal is a tidy single version of the truth. Intelligence and defense data inverts those assumptions. The subject is adversarial and works to avoid being resolved, the inputs include reporting prose, signals, and imagery-derived data with no shared schema, and classification levels mean the records cannot be pooled into one file and merged.
So MDM wants to collapse records into one golden row, while mission entity resolution deliberately does the opposite: it links the records that describe one entity and preserves each original with its classification and confidence intact. A golden record that overwrites its sources is an asset in a marketing database and a liability in a targeting package, because an analyst, and a commander, has to be able to see why two records were joined and to reverse the call if it is wrong.
This matters because every downstream product inherits the result. The Department of Defense has made integrating data across hundreds of separate systems a program-level priority through its Combined Joint All-Domain Command and Control (CJADC2) effort, and independent oversight describes the current state bluntly: analysts "collect, assess, and package the data by manually entering and transferring them into yet another system," and the goal is "a computing environment that effectively connects existing federated data across multiple systems and mission areas" (U.S. Government Accountability Office, GAO-25-106454, Defense Command and Control, 2025). The emphasis on connecting federated data, rather than migrating everything into one repository, is precisely the line between the two disciplines: MDM centralizes into a golden record, while mission entity resolution reasons across sources that stay where they are and stay owned.
The table below separates the two so each can be evaluated on its own terms. Entity resolution is the matching capability; master data management is the governance program that consumes it for an organization's own reference data.
| Dimension | Master data management (MDM) | Entity resolution |
|---|---|---|
| What it is | A governance program for an organization's core reference data | The capability that decides which records are the same real-world entity |
| Primary goal | One authoritative golden record per customer, product, or vendor | A linked entity with confidence and a trace back to every source |
| Data it assumes | Owned, cooperative, mostly structured reference data | Multi-source, adversarial, structured and unstructured, often unowned |
| Core question | What is the single version of the truth for this record? | Who is this entity across everything we hold, and what connects to it? |
| Treatment of sources | Collapses records into one golden record | Links records and preserves the originals, classification intact |
| Free text and signals | Generally out of scope; assumes defined fields | Extracts entity mentions from prose and ties in signals and imagery-derived data |
| Governance focus | Stewardship, data quality rules, policy, lifecycle | Match confidence, provenance, analyst adjudication, reversibility |
| Relationship | Uses entity resolution to decide what to merge | A core engine inside MDM, and useful on its own |
Neither column is wrong for its own job. MDM is the right discipline for governing an enterprise's own reference data. Entity resolution is what you need when the data is heterogeneous, partly unstructured, classification-constrained, and the subject is working not to be matched.
Yes. Entity resolution is the matching core an MDM program relies on to decide which incoming records describe an entity it already knows, so it can maintain one golden record rather than accumulating duplicates. In that sense entity resolution sits underneath MDM as a dependency.
The reverse is not true. Entity resolution does not need an MDM program around it, and in a mission setting you often explicitly do not want the MDM outcome. The goal is not a single overwritten record maintained by data stewards; it is a resolved entity that keeps every source visible so a match can be inspected, explained, and reversed. The same statistical matching can serve both, but the deliverable and the governance around it are different: MDM produces a curated master record, while mission entity resolution produces a provenance-preserving, analyst-adjudicable link.
That is why evaluating an MDM platform as if it were a mission entity resolution capability understates the problem. The matching math may carry over; the adversarial name handling, the multi-source heterogeneity, the classification awareness, and the refusal to overwrite sources do not come for free with a commercial master data program.
Use master data management when the problem is governing your organization's own reference data: deduplicating and maintaining one authoritative record for customers, products, suppliers, or locations, with stewardship and data quality policy around it. That is the job MDM was built for, and it does it well.
Use entity resolution when the real problem is resolving entities across many systems that were never designed to line up, a meaningful share of the data is free text or signals or imagery-derived, the same entity hides behind aliases and transliterations, classification limits what can be compared, and every resolved entity has to survive a briefing. In that environment a golden record is the wrong target. You need a linked, provenance-preserving entity, and you need the matching, scoring, and adjudication around it.
In most defense and intelligence settings you are not choosing MDM or entity resolution; you are fielding entity resolution as the capability, and you do not want the merge-into-one-record behavior that an MDM program is designed to produce.
Torch.AI builds government-owned reasoning infrastructure the customer can own and govern. Within it, NEXUS makes data meaningful: it extracts entities from unstructured text and gives multi-source records a common semantic representation, the step a structured-record master data program never handled. HALO then performs entity resolution and graph-based fusion, resolving the records that describe the same real-world entity across fragmented, multi-source systems, attaching confidence, and preserving a trace back to every source so the match can be inspected and reversed. The result is a linked, provenance-preserving entity rather than an overwritten golden record.
This reasoning layer complements existing systems of record rather than replacing them, so authoritative data stays intact and interoperable instead of being collapsed into one master record locked inside a proprietary model. That is the distinction at the center of the approach: a system of reason built on top of the customer's systems of record, not a new master database to migrate onto. Whether a specific deployment is government-owned (GOTS) or commercial (COTS) depends on the system the customer installs and purchases; the point is that the government-owned model is available to evaluate when ownership and control matter to the mission. You can see how this is packaged as a capability on the Torch.AI software page. For the full capability, see entity resolution for intelligence analysis.
If you are deciding whether a tool gives you a master data program or genuine mission entity resolution, require the following:
Scoping a capability? Bring these seven requirements to a call and we will walk each one against your environment and run it on a sample of your multi-source data, with provenance traced end to end: request a technical walkthrough.
No. Master data management is a governance program for an organization's own reference data, and its deliverable is one authoritative golden record. Entity resolution is the capability that decides which records describe the same real-world entity, and in a mission setting it produces a linked, provenance-preserving entity rather than an overwritten master record. MDM uses entity resolution; entity resolution does not require MDM.
MDM assumes owned, cooperative, mostly structured data and collapses it into one golden record. Mission entity resolution assumes multi-source, adversarial, partly unstructured, classified data and deliberately links records while preserving every source. A golden record that overwrites its sources is useful in a commercial database and a liability in a targeting package, where every match has to be traceable and reversible.
Yes. Entity resolution is the matching core an MDM program relies on to decide which incoming records describe an entity it already knows, so it can maintain one golden record instead of duplicates. The reverse does not hold: entity resolution is useful on its own and, in a mission setting, usually should not produce the single overwritten record that MDM is designed to maintain.
Use MDM to govern your organization's own reference data, with stewardship and data quality policy around a single authoritative record. Use entity resolution when data spans many systems, a meaningful share is unstructured, aliases and classification constraints are in play, and every resolved entity has to survive a briefing. In most defense settings you field entity resolution and do not want the merge-into-one-record behavior MDM produces.
A golden record is the single authoritative version of a master data entity, such as a customer or product, that a master data management program curates and that downstream systems read from. It is the target of MDM. Mission entity resolution deliberately avoids it, producing instead a linked entity that keeps every source visible so the match can be inspected and reversed.
Describe the problem.
Define the constraints. We will structure the session.
No demo.
No slide deck.
Real work.
Describe the problem.
Define the constraints. We will structure the session.
No demo.
No slide deck.
Real work.
