You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NLP.js allows for specifying entities of various types including regex and depending on configured settings can handle various builtin types such as number, ordinal, date, and time.
The JovoModel v4 structure is converted to an NLP.js corpus.json file but it appears that it only supports entities of type enum as can be seen from the interface that expects an options:
I'm submitting a...
Expected Behavior
NLP.js allows for specifying entities of various types including regex and depending on configured settings can handle various builtin types such as number, ordinal, date, and time.
These built-in entity types are defined based on specified packages such as builtin-microsoft:
https://github.com/axa-group/nlp.js/blob/581b945b19a4c0205d85e4b575b6542a4b69372b/packages/builtin-microsoft/src/builtin-microsoft.js#L85-L103
The JovoModel v4 structure is converted to an NLP.js corpus.json file but it appears that it only supports entities of type
enum
as can be seen from the interface that expects anoptions
:jovo-model/packages/jovo-model-nlpjs/src/Interfaces.ts
Lines 15 to 26 in 8880b15
Here is a sample corpus that shows an enum entity (
hero
) and a regex entity (email
):Full sample is here
Tasks:
Something like:
Current Behavior
Can only use enum types in NLP.js when you specify the model in Jovo Model v4 format.
Error Log
No error.
Your Environment
The text was updated successfully, but these errors were encountered: