Release notes
Version 3.3.3
- Release date: May 30, 2025
- Compatible platform versions: Work.AI 10.2.8+
The release focuses on enhancing escalation capabilities based on analyst decisions, improving data processing accuracy, and upgrading models.
The option to ignore middle names when comparing names is added to the AI Agent configutation, reducing false positives during entity matching.
The tag content preprocessing is improved by removing the 36th-character newline before sending multi-tag input to the NER engine. The update addresses SWIFT line limitations and ensures accurate hit text alignment with modified tag content, enhancing entity recognition accuracy.
To improve the error rate, we added the ability to automatically escalate hits. Now, hits are escalated if a hit hash was disabled by an operator for any reason or never released by an analyst. When configuring the AI Agent, you can now choose between auto-release, auto-escalate, or both options, ensuring no relevant hits are overlooked.
To maintain audit trails, we enabled saving analyst comments from historical data upload and using them in decision review hit comments. The changes are as follows:
Comments are loaded from a new T_COMMENTS column of the
hits.csvormessages.csvfiles.A message-level analyst comment is only used if a message has exactly one hit.
A hit-level comment takes precedence over message-level comments.
For the same hit hash, only the last hit comment stored in the hash_comment column of the pss_clds_hash_analytics_v1 Data Store is used.
In the Output configuration section, you can now select using a custom continuous learning (CLDS) report template instead of generating a report with standard columns.
The Tara API is updated to v1.2.5. No changes to input and output contracts are applied.
The AI Agent configuration is upgraded with the decision model v5.1.3 and Name Matcher v1.1.2 delivering the following improvements:
Adding cities to geo term preprocessing.
Introducing a specific preprocessor to remove currencies.
Revised preprocessing logic to improve overall accuracy in entity detection.
The NER model is upgraded to v2.3.0 incorporating the following changes:
Improved model predictions for the Organization (ORG), Location (LOC), and Person (PER) types.
Improved recognition of Middle Eastern personal and company names.
Improved recognition of personal and company names in cases when input breaks the expected SWIFT field format.
Bug fixes:
Fixed the configuration issue with quality control (QC) and CLDS reports when switching between data collection options. As a result, when consecutive reports are run, the date range configuration chosen in the first run does not supersede the configuration choice made in the second run.
Resolved the issue with incorrect offsets after merging entities with IDs, enhancing the reliability of entity annotations.
Resolved a number of issues by updating Name Matcher to v1.1.2:
Resolved the issue with the Geocoder producing no results when parsing enrichment data.
Resolved the issue with a country removed in one name and preserved in another.
Fixed the issue with the individual name's low score if matching on initials.
Fixed the issue with score calculation for names with uncommon tokens.