Knowledge Graph

One Company, Three Nodes

The same company often lives in five systems under three names. Load those rows straight into a knowledge graph and you get three nodes standing in for one real thing, each holding part of its relationships.

Loading The GraphWithout an identity layer
crm.accountsAcme Inc→ contract, account ownerNode 1
billing.customersACME Incorporated→ invoices, payment termsNode 2
support.orgsAcme→ 41 support ticketsNode 3

One company becomes three nodes, and its contract, tickets and invoices end up on different ones.

The Problem

Garbage Nodes In, Garbage Graph Out

A knowledge graph built on unresolved data does not fail loudly. It quietly represents “Acme Inc” and “Acme Incorporated” as two unrelated nodes and splits the relationships that should connect them: the contract hangs off one, the support tickets off the other, the board member off a third.

Every query on that graph is now partly wrong. Shortest paths go missing, centrality is diluted across duplicates, and an agent traversing the graph acts on each duplicate independently, multiplying the error at automation speed.

Entity resolution is what turns a graph of database rows into a graph of real-world entities. It has to happen before the load, and it has to keep happening as new data arrives.

Split Relationships

Edges that belong to one entity are scattered across its duplicates, so paths and neighbourhoods are incomplete.

Diluted Signals

Centrality, influence and risk scores are spread over several nodes instead of concentrated on the real one.

Agents Multiply Errors

An agent walking the graph treats each duplicate as a separate entity and acts on each of them.

The Solution

Resolve, Then Load

Run entity resolution before the graph load, not after it. Match the rows that describe the same real-world thing across every source, and create one node per entity, with edges from every source attached to it.

Then keep resolving as data arrives. A new record should join the node it belongs to instead of creating another one, and the node’s ID should never change, so edges, embeddings and saved queries keep pointing at the right place.

Three Rows, One Node
Source rows3 records
crm.accountsAcme Incacme.com · 100 Market St, SF
billing.customersACME Incorporated[email protected] · 100 Market Street
support.orgsAcmeacme.com · San Francisco, CA
Zingg
Graph node1 entity
ZINGG_ID · 3f9d-a1c4Resolved
Acme Inc
crm.accountsbilling.customerssupport.orgs

Contracts, tickets and invoices that hung off three nodes now connect to one.

One Node Per Entity

Every source row for the same company, person or product becomes part of one node.

Edges From Every Source

Contracts, tickets, invoices and ownership links meet on the same node.

Stable Node IDs

New data joins existing nodes, so the graph grows without fragmenting.

Where Zingg Sits

The Identity Layer Under AI

Zingg runs as a workload inside your data platform and gives every entity one persistent ZINGG_ID. Everything above it reads the same resolved entities.

Used by
BI & dashboardsAI agents & RAGOperational appsReverse ETLData science

Reads your tables in placeWrites golden records and ZINGG_ID backNo copies leave the platform

Your data platform
DatabricksSnowflakeMicrosoft FabricGCPAWS

The same layer powersCustomer Analytics & MarketingFinancial Crime & RiskPrivacy & ComplianceSupply Chain & ProcurementProduct 360Master Data Management

Resolved Nodes, Trustworthy Edges

One Node Per Real Entity

Zingg merges fragmented records into one entity with a persistent ZINGG_ID before it becomes a node.

Any Entity Type

People, households, companies, suppliers, products and locations, each resolved with a model trained on your data.

Keep The Graph Current

New and changed records join existing nodes through the incremental flow, so node IDs stay stable.

On Your Infrastructure

Zingg runs on Spark or natively in Snowflake, so the data behind your graph never leaves your account.

FAQ

Knowledge Graph Questions

Why resolve entities before building a knowledge graph?

Because a graph inherits every duplicate in its source data. Two records for one company become two nodes, and the relationships that should meet on one node are split between them.

Does Zingg replace my graph database?

No. Zingg resolves the entities and gives each one a ZINGG_ID. You load resolved entities and their ZINGG_IDs into the graph database you already use.

Do node IDs change when data changes?

No. The ZINGG_ID persists. New and updated records join the entity they match, so the node and its edges stay put.

Which entities can Zingg resolve?

Any entity you can describe with fields: customers, households, companies, suppliers, products, locations, patients and more.

Build The Graph OnReal Entities

Resolve entities in your own data platform before they become nodes.