Privilege results fields
Once the Populate Privilege Results pipeline step completes successfully, results will begin to populate on documents at about 2,000 documents per hour. To check if the results have been populated, run a search that looks at Priv::Prediction is SET and Priv Project=[the name of the current project] and confirm the document count matches number of documents in the original project saved search.
Some results are populated to fields directly on the Document object, while others are populated to aiR for Privilege Document Results Object fields and then reflected onto the Document object through the multiple object Priv field. See all fields that are name spaced with "Priv::".
Results will never be overwritten or updated after the completion of Populate Privilege Results.
Results fields
Following is a list of results fields and their descriptions:
Document field | Field type | Description | Notes |
---|---|---|---|
Priv | Single result object | Links the document to its corresponding aiR for Privilege Document Results object, which is used to reflect results onto the Document object via the Priv:: namespace. | This field can be ignored. |
Privilege Project | Multiple object | The project where this document was analyzed. | |
Priv:: Prediction | Single choice | Whether a document is Privileged or Not Privileged. | |
Priv::Category | Single choice |
The category of privilege is dependent on the Record Type field set during General Settings. Documents with an Email record type will have the following Not Privileged Categories:
Documents with an Email record type will have the following Privileged Categories:
All other documents will have the following Not Privileged Categories:
All other documents will have the following Privileged Categories:
|
For a list of privilege categories and their descriptions see Privilege categories. |
Priv::Rationale | Long text | A description for why the document received the prediction it did. | |
Priv::Considerations | Long text | A description of what might change the AI’s prediction. | |
Priv::Citation | Long text | Excerpt from the Document which demonstrates the prediction. | |
Priv::Error Details | Long text | Contains error details for result level errors | For a list of all document errors and their descriptions see Document errors. |
Priv::Ungrounded Citation Present | Yes/No | When the aiR results citation cannot be found anywhere in the document text. Review the Ungrounded Citation and corresponding results with caution. |
One of the citations has been identified as an Ungrounded Citation. Review the Ungrounded Citation in the Priv::Citations field, Rationale, and Consideration. For more information, see Ungrounded Citations. |
Priv::Draft Log Description | Long text | Draft Privilege Log entry. |
aiR for Privilege generates Draft Log Descriptions for all documents predicted as Privileged. Each description is crafted individually for every document based on the content within the extracted text and insights identified by the aiR for Privilege pipeline steps. The draft log description is typically structured with the following sections:
|
Priv Recipient Aliases (all email segments) | Multiple object | Lists all aliases who are recipients on an email. Includes all email segments. | |
Priv Sender Aliases (all email segments) | Multiple object | Lists all entities who are senders on an email chain. Includes all email segments. | |
Priv Recipient Entities (all email segments) | Multiple object | Lists all entities who are recipients on an email | |
Priv Sender Entities (all email segments) | Long text | Lists the entity that is sending the email |
Privilege categories
Following is a list of privilege categories and their descriptions:
Document type | Category | Description |
---|---|---|
Attachments/Standalone Documents | Attorney Involvement | Document includes information that reflects attorney advice. |
Attachments/Standalone Documents | Related to Legal Matter | Document reflects information about an ongoing legal matter but does not include advice from an attorney. |
Attachments/Standalone Documents | Legalese / No Privileged Content | Document includes lots of legal jargon and legal content, however does not reflect the advice of an attorney. |
Wholly Privileged | Email in its entirety reflects privileged information or reflects attorney advice. For example, an entire email chain is a discussion between an attorney and a client regarding legal advice. | |
Privilege Redaction | Email contains privileged information or attorney advice, but not all of its content is privileged. For example, an email chain that has privilege in the last in time email, but earlier emails in the chain do not contain privilege. | |
Privileged Individual / No Privileged Content | Email includes privileged individuals, but no attorney advice is being sought or given. | |
Email/Attachments/Standalone Documents | Borderline | Inclusion of privileged information is unclear. |
Email/Attachments/Standalone Documents | Not Privileged | No clear explanation for privilege |
Email/Attachments/Standalone Documents | Junk Document | Contains no useful information to analyze. For example, random characters or an empty document. |
Document errors
If aiR for Privilege encounters a problem when analyzing a document, it will not return results for that document. Instead, it categorizes the document as Errored and returns an error message in the Error Details column.
Error messages
Following are possible error messages and their descriptions:
Error message | Description |
---|---|
Failure to parse results | The large language model (LLM) encountered an error. |
System error occurred | The large language model (LLM) encountered an error. |
All citations have been identified as Ungrounded Citations. | All the Citations for this document have been identified as an Ungrounded Citation. For more information, see Ungrounded Citations. |
Document text is empty | The extracted text of the document was empty. |
Document text is too short to generate results | There was not enough extracted text to analyze in the document. |
Document text is too long to generate results | The document's extracted text was too long to analyze. |
Model could not process document | A communication error occurred between the large language model (LLM) and Relativity. |
If you receive an error message, review the document for privilege manually.
Ungrounded Citations
Ungrounded Citations occur when the aiR for Privilege results citation cannot be found anywhere in the document text. This is usually caused by formatting issues. However, just in case the large language model (LLM) is citing sentences without a source, aiR for Privilege marks it as a possible Ungrounded Citation.
When aiR for Privilege receives the analysis results from the LLM it checks all citations against the document’s extracted text to search for Ungrounded Citations.
If a document has a combination of at least one valid citation and an Ungrounded Citation:
- Review all results with caution.
- All Valid Citations and Ungrounded Citations will be written back to the Priv::Citation field.
- All Ungrounded Citations will be flagged in the Citation Field.
- All Rationale and Considerations will receive a warning: [Based on Ungrounded Citation]
- The Priv::Ungrounded Citation Detected field will receive a flag of Yes.
If a document consists of all Ungrounded Citations without a valid citation:
- The document will receive a Priv::Category of Errored.
- aiR for Privilege will not return results for that document.
- Review the document manually.