Senzing Globalization Guide

What languages does Senzing support?

Senzing utilizes UTF-8 encoding which allows for most languages of the world to be properly captured and processed. Beyond ingesting and storing data, Senzing analytics go further – taking into consideration domain, culture, and cross-script differences for comprehensive global entity resolution. Senzing provides native support for cross-script comparisons across many languages and writing systems, with entity-centric learning capabilities that allow it to discover attribute variations (including script variations) even when attributes cannot be matched in their original forms.

Advanced personal name comparisons

Supported cultural groups

Personal names present unique challenges in global entity resolution. Senzing leverages IBM's InfoSphere Global Name Management for culturally-aware name comparison. This world-class name library uses spelling patterns and country-of-association information to determine cultural provenance and optimize matching strategies.

Primary Cultural Groups

Southwest Asian

Culture Original Script Romanized
Afghan افغان احمد Afghan Ahmad
Arabic محمد حسن الشمري Mohammed Hassan Al-Shamri
Persian علی رضا Ali Reza
Pakistani محمد علی Muhammad Ali

European

Culture Original Script Romanized
Anglo Standard Latin script
French François Müller Francois Mueller
German Björn Müller Bjorn Muller
Hispanic José García Jose Garcia

Han

Culture Original Script Romanized
Chinese 王小明 Wang Xiaoming
Korean 김민수 Kim Min-su
Vietnamese Nguyễn Văn An Nguyen Van An

Additional Cultural Support

Culture Original Script Romanized
Indian राम कुमार शर्मा Ram Kumar Sharma
Indonesian Standard Latin script with diacritics
Japanese さとう ひろし Satou Hiroshi
Polish Łukasz Kowalski Lukasz Kowalski
Portuguese João da Silva Joao da Silva
East Slavic Александр Петров Aleksandr Petrov (Ukrainian, Belarusian, Russian)
Turkish Mustafa Özkan Mustafa Ozkan
Yoruban Adébáyọ̀ Ọlátúndé Adebayo Olatunde
Generic (catch-all for other cultures)

Culture identification for shared scripts

New in v4.4Starting in v4.4, Senzing distinguishes name cultures that share a script, so each name is handled with the rules for its actual culture. For example, Ukrainian names in Cyrillic are Romanized with Ukrainian rules rather than generic East Slavic ones.

Script Distinguishes Example
Han Japanese vs Chinese 佐藤 (Japanese) · 王伟 (Chinese)
Arabic Persian vs generic Arabic بهرام رادان (Persian) · محمد الفايد (Arabic)
Cyrillic Ukrainian vs generic East Slavic Володимир (Ukrainian) · Владимир (Russian)
Before v4.4, Japanese Kanji is not directly handled by Senzing and is treated as Chinese Hanzi when provided. Starting in v4.4, Japanese surnames written in Kanji match their Romanized spelling (佐藤 ↔ Satou); given-name coverage is partial and improving. Because Kanji and Hanzi share characters, some names may still be identified as the wrong one of the two cultures.

Organizational names

Senzing provides robust same-script organizational name matching across many writing systems and languages.

Same-script organizational name matching examples

Script Examples
Arabic Script الشركة السعودية للصناعات الأساسية ↔ الشركه السعوديه للصناعات الاساسيه
Cyrillic Script ООО “Газпром” ↔ Общество с ограниченной ответственностью “Газпром”
Latin Script with Diacritics Société Générale ↔ Societe Generale
Volkswagen Aktiengesellschaft ↔ Volkswagen AG
Japanese Script トヨタ自動車株式会社 ↔ トヨタ自動車
Korean Script 삼성전자주식회사 ↔ 삼성전자
Chinese Script 中国石油天然气集团公司 ↔ 中国石油天然气集团

CJK+English cross-script matching

New in v4Senzing v4 introduces native cross-script matching between CJK (Chinese, Japanese, Korean) and English organizational names without requiring reference data.

CJK English
中國銀行股份有限公司 Bank of China
토요타 자동차 Toyota Motor Corporation
ソニー株式会社 Sony Corporation
阿里巴巴集团 Alibaba Group
삼성전자 Samsung Electronics

For other cross-script language combinations, robust matching of organizational names may still require reference data containing multiple versions of names, as there is no consistency in how organizations handle name translation across scripts. Some organizations represent names phonetically (Romanize them), some translate (or translate parts), and some organizations rebrand when moving into new markets/scripts. For these scenarios, data providers or services that offer organizational name enrichment can be beneficial.

Romanized Burmese organization names

New in v4.4Starting in v4.4, common Romanized Burmese organization terms match their English equivalents:

Romanized Burmese English
Myanmar Burma
Kawporayshin Corporation

Enhanced address comparisons

New in v4Senzing provides cross-script matching capabilities for addresses. Starting in v4, native cross-script matching between CJK (Chinese, Japanese, Korean) and English addresses is supported without requiring reference data, representing a major improvement for global address resolution.

Address matching examples

CJK English
710000陕西未央区西安凤城十路118 118, Fengcheng 10th Road, Xi’an, Weiyang District, Shaanxi 710000
〒540-0002大阪府大阪市中央区1-1 1-1 Chuo-ku Osaka Osaka 540-0002
上海市浦东新区陆家嘴环路1000号 1000 Lujiazui Ring Road, Pudong New Area, Shanghai
〒150-0002 日本 東京都渋谷区渋谷1丁目1番1号 1-1-1 Shibuya, Shibuya-ku, Tokyo 150-0002, Japan
대한민국 서울특별시 강남구 테헤란로 152 (우편번호 06236) 152 Teheran-ro, Gangnam-gu, Seoul 06236, South Korea

New in v4.4Matching Japanese block-style addresses (丁目番号 ↔ 1-1-1), as in the Tokyo example, requires v4.4 or later.

For other language combinations, addresses can be challenging for entity resolution as they tend to have many data quality issues. Senzing has capabilities to handle native scripts for addresses, with the most effective processing occurring in native-to-native (rather than native-to-Romanized) scenarios.

For cross-script address comparison in non-CJK languages, using an address hygiene product to Romanize addresses and providing both native script and Romanized versions to Senzing can improve matching accuracy.

Getting started

Senzing provides comprehensive globalization capabilities out of the box. The breakthrough CJK+English cross-script matching capabilities introduced in v4 for both organizational names and addresses require no additional configuration - simply upgrade to v4 to benefit from these improvements.

For the rare cases requiring specific cultural tuning or advanced cross-script scenarios, contact Senzing Support for guidance on optimizing configurations for your specific use cases.