- Getting started
- Balance
- Clusters
- Concept drift
- Coverage
- Datasets
- General fields (previously entities)
- Labels (predictions, confidence levels, hierarchy, etc.)
- Models
- Streams
- Model Rating
- Projects
- Precision
- Recall
- Reviewed and unreviewed messages
- Sources
- Taxonomies
- Training
- True and false positive and negative predictions
- Validation
- Messages
- Administration
- Manage sources and datasets
- Understanding the data structure and permissions
- Create a data source in the GUI
- Uploading a CSV file into a source
- Create a new dataset
- Multilingual sources and datasets
- Enabling sentiment on a dataset
- Amend a dataset's settings
- Delete messages via the UI
- Delete a dataset
- Delete a source
- Export a dataset
- Using Exchange Integrations
- Preparing data for .CSV upload
- Model training and maintenance
- Understanding labels, general fields and metadata
- Label hierarchy and best practice
- Defining your taxonomy objectives
- Analytics vs. automation use cases
- Turning your objectives into labels
- Building your taxonomy structure
- Taxonomy design best practice
- Importing your taxonomy
- Overview of the model training process
- Generative Annotation (NEW)
- Dastaset status
- Model training and annotating best practice
- Training with label sentiment analysis enabled
- Train
- Introduction to Refine
- Precision and recall explained
- Precision and recall
- How does Validation work?
- Understanding and improving model performance
- Why might a label have low average precision?
- Training using Check label and Missed label
- Training using Teach label (Refine)
- Training using Search (Refine)
- Understanding and increasing coverage
- Improving Balance and using Rebalance
- When to stop training your model
- Using general fields
- Generative extraction
- Using analytics and monitoring
- Automations and Communications Mining
- Licensing information
- FAQs and more
Understanding labels, general fields and metadata
Before designing your taxonomy, it’s important to understand what should be captured by labels, general fields, and metadata, to meet your objectives. There should be minimal overlaps as they all complement each other.
Labels:
- Concepts, themes and intents
- E.g. ‘Change of address request’, ‘Urgent’, ‘Status update request’, etc.
- Should not be used to capture information that is present in the metadata
General Fields:
- Structured data points extracted from the text
- E.g. Policy numbers, trade IDs, URLs, dates, monetary quantities, etc.
Metadata:
- Additional structured information associated with each message
- Metadata properties can be user properties (defined and added pre-upload, e.g. NPS score), email properties (captured from emails, e.g. sender, recipients, domains, etc.), and thread properties (automatically derived by the platform for threaded data like emails and chats, e.g. # of messages in thread, thread duration, etc.)
Here are some of the key distinctions and similarities between labels and general fields. The two are typically used in combination for automation, but individually they serve different purposes:
The platform makes label predictions based on text of the message (for emails, this means the subject and body of the email), as well as some metadata properties. For general fields, it learns from the assigned span of text, and the context of the text surrounding that span.
