Why does LUIS regex entity doesn't recognize SPACE/Whitespace?

Question

Why does LUIS regex entity doesn't recognize SPACE/Whitespace?

sharms 1

Hi, I'm trying to add a luis regex entity with a space.
This is the regex pattern:
([a-zA-Z]{1,3}\d{1,6}\s){1,6}

Basically, I have two utterance that contain an identical entity: one without any comma, and the other has one.
Utterance: Get flight detail of ID TNW12345 bound for LA.
Utterance2: Check detail of plane number TNW12345,LA.

This is the reason why I created a regex pattern with space to differentiate the two entity.
But when checking the utterances, it won't recognize the entity.

Is this a bug?

romungi-MSFT 49,096 Reputation points Microsoft Employee Moderator

2020-07-15T10:07:37.627+00:00

@sharms Are you looking at TNW12345 and TNW12345,LA as separate entities?
Just looked up the above pattern with regex editors and it does differentiate them as is. So, i think the same behavior is seen with LUIS.

Does the below pattern work for your scenario when you add it to LUIS?

([a-zA-Z]{1,3}\d{1,6}\s){1,6}|([a-zA-Z]{1,3}\d{1,6}[,])[A-Z]{1,2}
sharms 1 Reputation point

2020-07-15T12:28:25.977+00:00

Yes, these are separate entities. I tried it in https://regex101.com/ and this is working.

The whitespace doesn't seem to be recognized in Luis.

Regex Entities
romungi-MSFT 49,096 Reputation points Microsoft Employee Moderator

2020-07-15T15:00:55.177+00:00

Just curious, I added the following regex pattern
([a-zA-Z]{1,3}\d{1,6}){1,6}|([a-zA-Z]{1,3}\d{1,6}[,])[A-Z]{1,2}

After entering couple of utterances it seems to recognize the required flight number and does not include any whitespace

When i test in portal the number is correctly recognized.

Is this the expected behavior for your app?
romungi-MSFT 49,096 Reputation points Microsoft Employee Moderator

2020-07-21T11:02:24.837+00:00

@sharms Please let us know if you got a chance to review the above pattern in your app?

Your answer

romungi-MSFT 49,096 Reputation points Microsoft Employee Moderator

2020-07-15T10:07:37.627+00:00

@sharms Are you looking at TNW12345 and TNW12345,LA as separate entities?
Just looked up the above pattern with regex editors and it does differentiate them as is. So, i think the same behavior is seen with LUIS.

Does the below pattern work for your scenario when you add it to LUIS?

([a-zA-Z]{1,3}\d{1,6}\s){1,6}|([a-zA-Z]{1,3}\d{1,6}[,])[A-Z]{1,2}
sharms 1 Reputation point

2020-07-15T12:28:25.977+00:00

Yes, these are separate entities. I tried it in https://regex101.com/ and this is working.

The whitespace doesn't seem to be recognized in Luis.

Regex Entities
romungi-MSFT 49,096 Reputation points Microsoft Employee Moderator

2020-07-15T15:00:55.177+00:00

Just curious, I added the following regex pattern
([a-zA-Z]{1,3}\d{1,6}){1,6}|([a-zA-Z]{1,3}\d{1,6}[,])[A-Z]{1,2}

After entering couple of utterances it seems to recognize the required flight number and does not include any whitespace

When i test in portal the number is correctly recognized.

Is this the expected behavior for your app?
romungi-MSFT 49,096 Reputation points Microsoft Employee Moderator

2020-07-21T11:02:24.837+00:00

@sharms Please let us know if you got a chance to review the above pattern in your app?

Share via

Why does LUIS regex entity doesn't recognize SPACE/Whitespace?

Your answer