ixp
latest
false
Important :
Communications Mining is now part of UiPath IXP. Check the Introduction in the Overview Guide for more details.
UiPath logo, featuring letters U and I in white

Communications Mining user guide

Last updated Aug 1, 2025

Understanding validation on extractions and extraction performance

The Validation page shows an overview of extractions performance, and helps you drill down into the individual performance of each extraction.

You can access the validation details in the Extractions tab from Validation. The Exractions tab is only available if you have extraction fields defined on your dataset.​

Performance overview

The default page of the Extractions tab from Validation is an overview using the All filter. This page provides the following summary statistics on the overall performance of extractions in the dataset:

  • Extractions Mean F1 score
  • Extractions Mean Precision
  • Extractions Mean Recall


Note: A low Extraction Mean F1 score is a sign of poor extraction performance​.

Individual extractions

Select individual labels to view the performance of individual extractions, that is, the label and its associated extraction fields.

For each extraction, you can notice the following values:

  • F1 score
  • Precision
  • Recall

For all of the extraction fields for the label, you can notice the following values:

  • Average F1 score
  • Average precision
  • Average recall

For the individual extraction fields, you can notice the following values:

  • F1 score
  • Precision
  • Recall


Confidence levels and LLMs

How the confidence levels work varies depending on the underlying LLM model that you use.

If you use the CommPath LLM

If you use the CommPath LLM, themodel assigns a set of confidence scores for each prediction (%).

CommPath calculates and returns the following:

  • Occurrence confidence: The likelihood that the detected occurrence corresponds to the assigned label.

  • Extraction confidence: The confidence in the correctness of the extracted content.

These confidence values enable downstream automations to filter out extractions with confidence levels below a set label threshold. If you set an appropriate threshold, you can ensure that only predictions that meet a desired confidence level are used in workflows.

If you use the Preview LLM

The Preview LLM for Generative Extraction provides a single label occurrence confidence value for each extraction, replacing both the occurrence confidence and the extraction confidence. This approach differs from CommPath, which returns separate confidence values for each extraction.

Note:

Returning the label confidence helps filtering out extractions downstream if needed, allowing users to improve the precision of some results.

Automating with Generative Extraction

Note: If you have previously built automations with general fields and you plan to build automations using Generative Extraction, the API endpoint and activities required are different than what you have previously used.​

This section describes the outputs of the Get Stream Results activity. For more details, check Communications Mining™ dispatcher framework.​

To automate with Generative Extraction, you must first understand the contents of the outputs of your extractions.​

Occurrence confidence refers to how confident the model is around the number of instances a request might occur on a message, that is, how many times an extraction might occur. ​

As an example, to process a statement of accounts into a downstream system, you always need an Account ID, PO number, the payment amount, and the due date.

Check the occurrence confidence example in the following image. It shows how the model can confidently identify that there are two potential occurrences where you need to facilitate this downstream process​.



Extraction confidence

Extraction confidence is the confidence of the model about its predictions. This includes how accurate it thinks it was in predicting the instance of a label and its related fields. It also includes the confidence of the model in correctly predicting if a field is missing.

Consider the same example as before. To process a statement of accounts into a downstream system, you always need an Account ID, PO number, the payment amount, and the due date.

However this time, the PO number is not present on the message, or the due date, only the start date.

The extraction confidence from this example is the model's confidence about identifying if the values for each field associated with the label are present. It also includes the model's confidence in correctly predicting if a field is missing.

In this case here, you do not have all the fields you need, to be able to fully extract all the required fields.



Payload example

Check the following example output of what the Get Stream Results activity returns:


Stream refers to the threshold you set in Communications Mining, and if the message meets this threshold.

Instead of filtering predictions based on thresholds, this route returns which prediction confidence met the thresholds.

In other words, if your thresholds were met, stream is returned. If not, then this value is empty.​

Note:
  • The previous image contains a sample snippet to explain the different components, not the full output of a Generative Extraction response. ​Additionally, where there are multiple extractions, it is conditioned on the extractions before it.​ For labels without extraction fields, the occurrence confidence is equivalent to the label confidence that you can view in the user interface.
  • If the model has failed to successfully extract all of the fields in a message because there are too many fields, it will return an extraction in the stream response that has an occurrence confidence and an extraction confidence with values of zero.​

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo
Trust and Security
© 2005-2025 UiPath. All rights reserved.