Communications Mining
Plus récente (Latest)
False
Guide de l'utilisateur de Communications Mining
Last updated 2 juil. 2024

Meilleures pratiques et considérations

Don't split words

The highlighted general field should cover the entire word (or several) in question, not just part of it. Don't include additional spaces at the end of the field.



Don't partially review fields

Similar to labels, don't partially review your general and extraction fields.​

  • General fields are reviewed at the paragraph level, not the entire message level. When you review a paragraph for fields, review all the fields in the paragraph.

    Not confirming a field in a paragraph where you have labelled other fields, tells the model that you don't consider it a genuine example of the predicted field. This is reflected in the validation scores and the general field performance.

  • Extraction fields are reviewed at the message level, not just the paragraph level. When you review an entire message for fields, review all the fields in the message.

    Not confirming a field in a message where you have labelled other fields, tells the model that you don’t consider it a genuine example of the predicted field. This is reflected in the validation scores and extraction field performance.

Field level considerations

Remarque : Field level considerations and extraction and label performance are the most important things to remember when assigning both general and extraction fields are.
  • Global fields cannot overlap with each other, or with another example of itself.
  • Global fields and extraction fields can overlap with each other.
  • You can use the same span of text as many times as needed by different extraction fields​.
  • There is currently no general field normalization preview in Communications Mining. Fields that should be normalized will get normalized in the downstream response. Normalization in Communications Mining will be available in the model in the future​.
  • If a child label has extractions on it, its parent doesn’t inherit the extraction examples automatically. For labels, its parent automatically inherits the extraction examples.

Extraction and label performance

  • Providing additional extraction examples does not improve the performance of a label. To improve the performance of a label, focus on label-specific training.
  • Improving label performance allows you to increase the likelihood that you capture occurrences where a label (and subsequently its extractions) should have been predicted.

    To improve the performance of your extractions, provide validated examples on the extractions itself.

Cette page vous a-t-elle été utile ?

Obtenez l'aide dont vous avez besoin
Formation RPA - Cours d'automatisation
Forum de la communauté UiPath
Logo Uipath blanc
Confiance et sécurité
© 2005-2024 UiPath. All rights reserved.