Microsoft

Language Understanding (LUIS)

Welcome to the LUIS API Forum

(Language Understanding Intelligent Service)

Categories

Documentation – Any ideas or suggestions for the API Reference or Documentation.

Language Support – Submit a request to have a particular language supported.

luis.ai WebApp – Ideas and suggestions for luis.ai and functionality used through the WebApp.

Programmatic API – Any ideas or feedback pertaining to features or enhancements to LUIS programmatic API.

Samples & SDK Request – Let us know if you would like to see a tutorial/sample or a SDK provided.


                               Attention!





We have moved our Customer Feedback & Ideas for Azure Cognitive Services portal to the Azure Feedback Forum.





Please go to the link below to access our new Feedback and Ideas Page.



  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Set priority in Patterns

    I am using pattern recognition to catch entities with a variable size. Here are situation that i am trying to catch

    1- {entity1} (has| had| have) [the] {entity2}

    2.1- {entity1} (has| had| have) the {entity2}

    2.2- {entity1} (has| had| have) {entity2}

    i tried the 1 pattern or the 2.1 and 2.2 at the same time.
    The problem is that when i enter: "Person have the properties"

    the entity2 is marked as "the properties" instead of just "properties"
    It would be nice to have a way to set priority in the patterns to avoid this problem

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Patterns  ·  Flag idea as inappropriate…  ·  Admin →
  2. The result of pattern matching is not included in the LUIS Endpoint API.

    I can confirm the matched pattern as "Top matched pattern(s)" with the portal screen (luis.ai), but I can not do with the Endpoint API. Please add the "Top matched pattern(s)" to JSON returned by Endpoint API.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Patterns  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support Entity whose name including Parenthesis

    When using patterns, I found that I can not refer to an entity if its name includes parenthesis, i.e. (). I understand that brackets [] and braces {} are illegal since they have special functions in patterns, but why parenthesis are not permitted?

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Patterns  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support phrase lists inside patterns

    Given the following pattern:
    tell me when I get {money}

    And the following phrase list:
    tell me
    let me know

    I get the following pattern matches:
    tell me when i get 100 eur -> MATCH (expected)
    let me know when i get 100 eur -> NO MATCH
    when I get 100 eur -> NO MATCH (expected)

    Supporting phrase lists inside pattern would help unclutter and simplify patterns.

    5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Patterns  ·  Flag idea as inappropriate…  ·  Admin →
    Resolved  ·  Luke Bayler responded

    Hello,

    Phrase lists in LUIS do not support this. But, to enable this scenario, LUIS has Grouping and ORing functionality, so [tell me | let me know] when I get 100 eur will meet your scenario.

    Thanks,
    Luke

  5. Improve brackets in patterns

    A pattern such as sho[w] should match both "sho" and "show". Below are some examples of the current behavior. There are many more use cases in German and other languages. This feature would simplify and shorten pattern creation significantly.

    Pattern: [show][sho] me the cash
    Match: sho me the cash
    Match: show me the cash

    Pattern: sho[w] me the money
    Match: sho me the money
    No match: show me the money
    Match: sho w me the money

    7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Patterns  ·  Flag idea as inappropriate…  ·  Admin →
    Under Review  ·  Luke Bayler responded

    Hello,

    Our pattern engine currently doesn’t support this because anything in between spaces is considered as a token. We can look into adding this.

    In the meantime, you can do this with pipes (“|”). For example, (show | sho) me the money.

    Thanks,
    Luke

  6. Support Negate Condition to Pattern

    Currently pattern supports entity by {} bracket and optional by [] bracket.

    I think we can have negated condition like [^{}] (regex-like)

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Patterns  ·  Flag idea as inappropriate…  ·  Admin →
    Resolved  ·  Luke Bayler responded

    Hello,

    Anything not in the patter means that the pattern will not get detected correctly.

    Thanks,
    Luke

  • Don't see your idea?

Feedback and Knowledge Base