Resolve is an entity resolution API that makes partial records complete, matches one entity against another, and assists in de-duping and normalizing datasets. This demo allows you explore how Resolve works: add fragmentary and partial information to the boxes above, and click 'Resolve' see what we can do with it; click 'start over' to clear the form and see this text again.

The following examples should give an idea of how Resolve works, and how we use the attributes provided:

• Partial name match combined with coordinate proximity (Ino Cafe). Lon/Lat searches restrict the candidate list and usually produce good Resolutions; the coordinates provided must be in proximity to the desired match.
• Name, Address and State match (McDonald's). There are thousands of McDonald's, but providing the street address gives us the ability to disambiguate amongst them.
• Name and Postcode match (Urasawa) 'Ursawa' is an uncommon name, so this is easily resolved with the addition of postcode granularity.
• Name, city and state match (Pizza Hut). This would not resolve if there were more than one Pizza Hut in Wayne, PA.
• Name only (Paneitz Salvage). There's only one of these, so we can resolve it on the name alone.
• An example of a failed Resolve using Name and Zip only (Starbucks). Here there are three Starbucks in this zipcode, and an insufficient amount of data was passed to the service to disambiguate between them.

Remember: the more information you provide the service, the better the Resolution. We're always improving this API -- if you have an example that you think should resolve unequivocally but does not please post it to our developers forum and we will investigate. See the Resolve Developer Docs and the Resolve Launch Post for more information.