> For the complete documentation index, see [llms.txt](https://docs.zingg.ai/zingg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingg.ai/zingg/interpreting-results/explainability-and-statistics.md).

# Explainability and Statistics

Understand how a specific entity cluster was formed, which records matched, which did not, explore the cluster insights.

{% hint style="info" icon="right-long" %}
Enterprise only.
{% endhint %}

Once you have run a match or `runIncremental` phase, you can use the `explain` phase to look under the hood of any cluster. Provide a Zingg ID, and Zingg shows you exactly how that cluster formed, which record pairs were matched probabilistically, and which records did not directly match each other.

This is useful for model validation, governance, explaining results to business stakeholders, human-in-the-loop reviews with domain experts, and building confidence in production pipelines.

{% hint style="success" icon="right-long" %}
`explain` currently covers probabilistic matches only. Deterministic matches are not included\
in explain output at this time. Clusters formed primarily through deterministic matching rules may return empty results.

If you get empty results, verify that the Zingg ID you are querying exists in your match output before running explain.
{% endhint %}

Explain answers "why did these specific records end up together?" for one cluster at a time. If you instead want aggregate, run-level visibility, how many clusters formed, how dense they are, how much of the matching came from deterministic rules versus probabilistic scoring, and whether clusters are stable across incremental runs, that's what **output statistics** provides, at three levels: a run-wide **Summary**, per-**Cluster** detail, and per-**Record** detail.

{% hint style="success" icon="right-long" %}
**Read more**:

* For the step-by-step explain phase task with code - [Explain a specific cluster](/zingg/interpreting-results/explainability-and-statistics/explain-a-specific-cluster.md)
* For record-level and per-cluster match-quality metrics - [Output statistics](/zingg/interpreting-results/explainability-and-statistics/output-statistics.md)
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zingg.ai/zingg/interpreting-results/explainability-and-statistics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.