Validate Entities

The Validate Entities pipeline step locates email addresses and other alias formats used to communicate within your data set, assigning them an individual owner or entity. It then determines attributes about the entity, and predicts if an entity is in a legal role that will drive privileged predictions on documents they communicate in. Our model considers language from documents, extracted email signatures, and other information to make a prediction of Legal Role or Not Legal Role.

This step will influence the default Entity Privilege Designation which can be revised on the Confirm Entity Privilege Designation step.

Requirements

Following are requirements for the Validate Entities pipeline step:

When the system runs Validate Entities, it will identify entities and their corresponding aliases and populate them on the Entities (Priv) tab.
Once you've performed the Apply Annotations action, entities not annotated on the Annotator Decision field will take their Prediction field value as truth to calculate the default Privilege Designation.
Any Entity with the Annotator Decision field value of Legal Role must have both First Name and Last Name fields populated.

Actions

Once the Match Equivalent Domains pipeline step is complete, the system will automatically run Validate Entities and the status will change to Run In Progress.

When the Validate Entities step completes, the status on the step changes to Ready to Apply Annotations and the system enables the Apply Annotations action button.

Before completing this step, you must annotate the entities identified by the Validate Entities step to confirm or deny the Predictions on the Annotator Decision field. Quality check (QC) the decisions made by your team for accuracy. See Annotating entities for more details.

To apply annotations for Validate Entities:

Navigate to the Projects (Priv) page.
Select the project you would like to interact with.
Locate the Validate Entities step in the Pipeline Steps category.
Click the Apply Annotations button within the Actions column next to the Validate Entities step.
The Apply Annotations button will only be available when you have successfully performed the Run action.
A pop-up window displaying annotation details will appear. Review the number of Total Entities Annotated and Entities Missing Annotator Decision.
Click Confirm to indicate that you have performed annotations.

Entities missing an Annotator Decision once you Apply Annotations will use their Prediction field value as their decision. If the Prediction field value is incorrect, it may result in a Privilege Conferring individual being considered Privilege Neutral. This will lead to privileged documents being predicted as Not Privileged due to the lack of a Privilege Conferring individual presence (lower recall). The Privilege Designation of an Entity will be automatically generated during the Confirm Entity Privilege Designations step, and Case SME Revisions can be used to override that default designation. It is recommended to wait until Confirm Entity Privilege Designation to apply the Case SME Revision to avoid unnecessary annotations.

The Validate Entities step status will change to Apply Annotations In Progress. The system will disable the Apply Annotations action button until the status updates.

Upon the successful completion of the Validate Entities Apply Annotations action, the status on the step will change to Completed. You can then move on to the Confirm Privilege Status pipeline step.

Errors

If the status of a pipeline step becomes Run Failed or Apply Annotations Failed then there is an error in the action. Check the Error Details field within the Pipeline Steps category or refer to the error message that appears on screen for detailed error information including steps to resolve the issue.

For more information, see aiR for Privilege errors.