Skip to content
This repository has been archived by the owner on May 5, 2021. It is now read-only.

Intent Miss-classification with number intent #723

Open
engahmed1190 opened this issue Aug 21, 2020 · 2 comments
Open

Intent Miss-classification with number intent #723

engahmed1190 opened this issue Aug 21, 2020 · 2 comments

Comments

@engahmed1190
Copy link

Describe the bug
I am having a problem with the new NLU pipeline,

image

Numbers are misclassified when tested alone. previously it was working fine.

Old NLU Pipeline

pipeline:
  - name: WhitespaceTokenizer
  - name: CountVectorsFeaturizer
  - name: EmbeddingIntentClassifier
  - BILOU_flag: true
    name: CRFEntityExtractor
    features:
      - [low, title, upper]
      - [low, bias, prefix5, prefix2, suffix5, suffix3, suffix2, upper, title, digit, pattern]
      - [low, title, upper]
  - name: rasa_addons.nlu.components.gazette.Gazette
  - name: EntitySynonymMapper

Please help me to address this issue. Thanks in advance

@pheel
Copy link
Contributor

pheel commented Aug 25, 2020

What is the expected/previous behavior? If digits only appear under that one intent it's very likely the trained model will do this.

@engahmed1190
Copy link
Author

Previously it was classified as none which is correct but Currently it is mapped to the intent that contains number. How may I address this, any workarounds

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants