Zingg 3.3 Model Treats Similar Records as Unique Despite Fuzzy Match Configuration—Is This Expected?

Hi Sonal, "I’m currently working with Zingg version 3.3 and have successfully created a new model using my own dataset. I encountered a scenario where two records appear to represent the same individual: Data 1: Name: C.V. RAVISEKAR VASUDEVAN PAN: APPER5089R Mobile: 9876543210 Data 2: Name: RAVISEKAR CV PAN: APPER5089R Mobile: 9876543210 Despite the strong similarities—especially in PAN and mobile number—the model has classified them as unique records instead of a match. I defined the config in the same order (Name, PAN, Mobile) using the fuzzy match type. Would Zingg work in this manner, or am I missing something?" This is a scenario we had previously discussed at the help desk. Unfortunately, the issue still remains unresolved on my end. I’ve tried adding similar data as training samples, but these types of scenarios are still being classified as unique. We also attempted creating a new model using different datasets, but these records continue to be treated as unique cases. Would Zingg work in this manner, or am I missing something?"