Entity Resolution Configuration & Parsing Health Checks
Entity Resolution (ER) and good Entity quality underpin all Quantexa deployments. The accuracy of Entity configuration and parsing are two areas that impact Entity quality. These articles outline Entity Resolution (ER) health checks and Parsing health checks to be carried out by the development team on deployments. This allows the team to identify, prioritize, and fix any potential underlying issues that could be reducing Entity quality. These checks must be completed as part of the initial deployment, but also periodically over the lifetime of the deployment. New product functionality, and data changing, may mean configuration needs to be changed, or enhanced over time. Topics covered: Entity Resolution Health Checks Pre-requisites Resolver JSON configuration health check steps Perform a comparison to the latest core Resolver JSON configuration Review configured Element exclusion criteria Review configured exclusions for Compounds in the relevant template Compound model health check steps Are all required Compounds being generated in ETL for the relevant Document types? Are Compounds being generated to populate elements required for exclusions in other Compounds? Do the traversals all look sensible? Do you have good coverage of unit tests? Parsing Health Checks Pre-requisites Parsing health check steps Is your deployment using the latest versions of Parsers? Has your deployment applied custom Parsing functions or wrappers? How does your Parsing compare to best practice Parsing? How well are the Parsers performing per source and country? How well-populated are the Parsed fields?
Best Practice Guide For Validating Entity Resolution ✅
When either validating or understanding the Entity Resolution within the Quantexa User Interface (UI) it is recommended to approach the process using the following steps: Understand the Entity Resolution Levels required Do a quick initial screen of the Entity and Documents Use the Entity Lab to check for possible over-linking and under-linking. If you aren't familiar with using Entity Lab, be sure to check out Tips & Tricks for Understanding Entity Lab. Document outcomes and raise any required changes to update the resolution Read the full best practice guide (login required): 2. Best Practice For Validating Entity Resolution - Quantexa Community When either validating or understanding the Entity Resolution within the Quantexa User Interface (UI) it is recommended to approach the process using the following steps: Understand Entity Resolution Levels Required It is critical to initially understand the attitude to both false positive / negative resolution. This is…Best Practice for Selecting a Sample for Entity Resolution Validation
When validating Entity Resolution on a project it's important to ensure a wide range of entities and cases are selected as a sample for review. It is also important to regularly change your sample to ensure the resolution is not tuned to a small subset. Learn more & read the full article (login required): 1. Best Practice for Selecting a Sample for Entity Resolution Validation - Quantexa Community When validating Entity Resolution on a project it's important to ensure a wide range of entities and cases are selected as a sample for review. It is also important to regularly change your sample to ensure the resolution is not tuned to a small subset. 📝Note: The key entities to review include individuals, businesses and… Read more from our Entity Validation Best Practice collection (login required): Entity Validation - Best Practice - Quantexa Community When validating Entity Resolution on a project it's important to ensure a wide range of entities and cases are selected as a sample for review. It is also important to regularly change your sample to ensure the resolution is not tuned to a small subset. 📝Note: The key entities to review include individuals, businesses and…
Using Batch Resolver Tools for Entity Resolution
Entity Resolution (ER) is a key part of the Quantexa solution. It is important to understand how changes to improve Entity Resolution can affect the entire Entity population. If you are new to Entity Resolution at Quantexa, take some time to familiarize yourself with the concept introduced on our Documentation Site page 'Introducing Entities and Entity Resolution'. This article explains how to use outputs from Batch Resolver tools and reports to review and monitor ER. These include: The Input Report which provides summary statistics and calculations on the input data for Batch Resolver. The Compound Report which provides summary statistics on the excluded Compounds. The Entity Report which gives stats on the sizes and distribution of Entities. Read the full article (login required): Using Batch Resolver Tools for Entity Resolution - Quantexa Community Entity Resolution (ER) is a key part of the Quantexa solution. It can be hard to see how changes to improve ER affect the entire Entity population. This article explains how to use some outputs from Batch Resolver tools and reports to review and monitor ER. Note: If you are new to Entity Resolution at Quantexa, take some…
Business Analyst Entity Review Checklist 📋
Conducting a focused evaluation of Entity Resolution is a critical step in the Entity Maturity Checklist. This article provides a step-by-step guide and scoring system to help Business Analysts assess the state of Entity Resolution within their deployment. Each section includes a scoring guide, with scores ranging from 0 to 4: Lower scores indicate that Entity Resolution has been under-prioritized, potentially concealing unresolved issues or misrepresenting its effectiveness. Higher scores reflect alignment with best practices and meaningful progress. The checklist is divided into three parts: Documentation and Analysis: Is Entity Resolution documentation and analysis aligned with best practices? Problem Solving and Understanding: Has the deployment deeply investigated and understood Entity Resolution challenges? Impact Assessment and Improvement: Are Entity Resolution improvements actively prioritized and implemented? Read the full Business Analyst Entity Review Checklist (login required) to explore detailed scoring criteria and practical steps for ensuring Entity Resolution maturity.
Entity Quality: The Good, the Bad and the Ugly 🎭
This article looks at Entity Quality and how to judge it based on business need. It introduces Overlinking and Underlinking as a product of Entity Resolution, and these two concepts are two ends of a continuum. Entity Quality is the bedrock of any Entity Resolution (ER) based solution and has implications up and down the Quantexa stack. Getting this right is an essential part of an effective deployment. In this article we look at the basics of how to frame this problem and highlight that context is king for each solution. Read the full article here (login required): 3. Entity Quality: The Good, the Bad and the Ugly - Quantexa Community This article looks at Entity Quality and how to judge it based on business need. It introduces Overlinking and Underlinking as a product of Entity Resolution and these two concepts are two ends of a continuum. Note: All the examples in this article are fictional to illustrate how to approach Entity Quality. Entity Quality…
New guide: Using the Entity Quality Underlinking (EQU) tool for the first time 📖
The Entity Quality Underlinking (EQU) tool is a powerful resource for tuning and monitoring Entity Resolution. Using the Entity Quality Underlinking (EQU) tool for the first time is a detailed guide to implementing the Entity Quality Underlinking tool, including its design, implementation tips, and practical use cases. Why is the Entity Quality Underlinking Tool useful? The Entity Quality Underlinking Tool helps you: Identify underlinked Entities and analyze root causes through manual examination in the UI. Measure the extent of underlinking over time, especially when tracking this metric in Production. Adjust Entity Resolution templates to address Overlinking issues identified earlier. What does the Entity Quality Underlinking Tool do? Monitoring and Tuning: The Entity Quality Underlinking Tool supports both tuning iterations and ongoing Entity Resolution monitoring. Analysis: It observes the similarity of Entity Elements and identifies potentially underlinked Entities. Output: The Entity Quality Underlinking Tool generates: Summary Statistics for tracking improvement or ongoing performance metrics. Potentially Underlinked Entities for investigation in the User Interface (UI). What’s in the guide? Step-by-step instructions for implementation. Design considerations for effective use. Tips to ensure smooth implementation and accurate results. Read the full article for a comprehensive understanding of how to integrate the Entity Quality Underlinking Tool into your Entity Resolution processes (login required): Using the Entity Quality Underlinking (EQU) tool for the first time - Quantexa Community This article details the implementation of the Entity Quality Underlinking (EQU) tool, developed to assist when tuning Entity Resolution. What is EQU? The EQU tool is used as part of Entity Resolution Tuning and BAU Entity Resolution monitoring. It observes the similarity of your Entities' Elements and identifies whether…Tips and Tricks for Understanding Entity Lab
Entity Lab can be quite complex to understand and review when searching for Entity Resolution problems. To help with this, we've compiled some tips and tricks for what to watch out for that may help you quickly understand the health of your entities as well as some common shapes you may encounter, including: Signs of Possible Overlinking Signs of Underlinking Possible Aggregation Issues Read the full article: Tips & Tricks for Understanding Entity Lab (login required) Tips and Tricks for Understanding Entity Lab - Quantexa Community Entity Lab can be quite complex to understand and review when searching for Entity Resolution problems. Below are some tips and tricks for what to watch out for that may help you quickly understand the health of your entities as well as some common shapes you may encounter. Signs of Possible Overlinking Look for lots of…
Why does Entity quality matter?
You might have read that Entity Resolution (ER) and good Entity quality underpins all Quantexa deployments. But what does that mean? Take a look at our article Why Entity Quality Matters to learn some of the wide-ranging benefits having good Entity quality will bring to your deployment. This includes how Entity quality impacts: Scoring Investigation processes Quantexa Batch performance 2. Why Entity Quality Matters - Quantexa Community You might have read that Entity Resolution (ER) and good Entity quality underpins all Quantexa deployments. The purpose of this article is to detail the wide-ranging benefits having good Entity quality will bring to your deployment. In this article we will look at how Entity quality affects the following areas of a…Auto-coldlisting - primary vs secondary Elements
Auto-coldlisting is a powerful feature when it comes to tuning and improving Entity Resolution. Auto-coldlisting enables you to deactivate Compound values when sufficient contrary information, in the form of Elements, has been found to suggest that the Compound is overlinking distinct real-world Entities. Typically, Quantexa recommends using Elements that are primary to an Entity Type when Auto-coldlisting. For example, for individual Entities it is recommended to Auto-coldlist on primary Elements such as forename, middle name, surname, or date of birth as opposed to secondary Elements such as postcode, road, phone number. The reason for this is it is reasonable for an individual to have multiple addresses or phone numbers. For more and to see a worked example for how Auto-coldlisting is applied read the full article in our Community library: 1. Auto-coldlisting - Primary vs. Secondary Elements - Quantexa Community Typically, Quantexa recommends using Elements that are primary to an Entity Type when Auto-coldlisting. For example, for individual Entities it is recommended to Auto-coldlist on primary Elements such as forename, middle name, surname, or date of birth as opposed to secondary Elements such as postcode, road, phone number.…
