Skip to main content

Entity linking by custom attributes

Updated over a year ago

Introduction

For users of both Platform and Bridge products, or those utilising Bridge through Platform, we offer a robust feature for linking multiple entities to an RFI through customisable and priority-based attribute matching.


Configuring Attribute Mapping

To utilise this feature effectively, you need to specify which data fields should be used for linking and the priority of these fields.

🚨 Currently, the mapping is handled by Salv.


However, it is crucial to emphasise that for this feature to function, we require your input: you need to inform us which data fields to map and indicate their priority. If you are unsure about which fields to map, please feel free to reach out to us for assistance.

  1. Identify Data Fields: Determine which fields from the RFI message template will be used to search corresponding fields in the entity data (Person or Transaction data fields).

    • Example: firstName and lastName in the message template should correspond to first_name and last_name in Person data fields.

    • We apply exact matching when comparing mapped attributes.

    Figure showing an example Person linked to an RFI based on company name and country fields

  2. Set Priority of Attributes: Organise the fields in a priority list, which the system will follow in a top-down approach during the matching process.

    • For instance, if first_name + last_name is set as a higher priority than company_name + country, the system will first attempt to find matches based on the first set of attributes. If no matches are found, it will proceed to check the next set in the priority list.

    • To optimise the effectiveness of this feature, it is advisable to rank attribute combinations from narrow (more specific) to broad (more general). This approach increases the likelihood of precise matches and efficient data retrieval.

      • Example rankings might include:

        • email + first_name + last_name + city

        • first_name + last_name

        • phone_number + contact_name

  3. id Matching: If Person and Transaction id mapping is configured, it will always be attempted first for its reliability in providing exact matches. If no match is found, the system will proceed to check the attribute combinations as configured.


This feature provides you with powerful tools for automating and refining the entity linking process in RFIs. By clearly defining and communicating your requirements, you can significantly enhance the accuracy and efficiency of your data handling. To configure your system with the entity linking features, please contact our support team.

Did this answer your question?