Real-Time Entity and Network Generation Action Set

You can define conditions for splitting entities by using the splitConflictingEntities parameter. You can split an entity on the basis of whether the entity contains conflicting compound values by using the conflictingCompoundValues subparameter. For example, suppose that Social Security number is a compound that you know uniquely defines an entity and that no entity should ever have multiple Social Security numbers. You can specify this compound type in the conflictingCompoundValues subparameter. If an entity contains multiple values of any compound type that is listed in the conflictingCompoundValues subparameter, then the entity is split in a way that creates one or more entities such that no resulting entity has multiple values for that compound. Specifying this parameter requires that all compound values for entities of a given type be checked for conflicts. This process incurs a performance cost, so you should not use it to correct issues that you can already resolve by using the compound and entity specification.

By using the doNotSplit sub-subparameter, you can restrict what components of the entity are split by specifying document type and compound type pairs. If you specify a document type and a compound type in this sub-subparameter, then no compound value of the specified compound type can be split from any document of the specified document type. Conflicting compound values are not split if the only way to split these values is to split a document and compound whose types are specified in the doNotSplit sub-subparameter.