IBM Watson™ Ideas

Welcome to the IBM Watson™ Ideas Portal

We welcome and appreciate your feedback on IBM Watson™ Products to help make them even better than they are today!

If you are looking for troubleshooting help or wondering how to use our products and services, please check the IBM Watson™ documentation. Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal.

If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.

NLQ should not search numeric fields that specify e.g. offset of entity within text

The json document ingested into WDS ends up with this out of the box NLU detected "Jobtitle" entity, with location offset ending at 2016:

                        "count": 2,
                        "text": "program manager",
                        "mentions": [
                                "text": "program manager",
                                "location": [
                                "text": "program manager",
                                "location": [
                        "relevance": 0.495976,
                        "type": "JobTitle"


When I issue the NLQ query  "2016" thinking that NLQ will only search ALL TEXT FIELDS, this document is returned. No other mentions of 2016 is in the document.

Enhancement request is that WDS NLQ not search fields that do not represent CONTENT of the document. An numerical offset does not reflect the contents of the document and is causing false positives in search results.

  • Guest
  • May 13 2019
  • Future Consideration
Why is it useful?
Who would benefit from this IDEA? All customers, but this is an issue that was discovered with Project Daisey
How should it work?
Idea Priority
Priority Justification
Customer Name
Submitting Organization
Submitter Tags
  • Attach files
    20 Sep, 2019 01:10am

    Count and location in this example are both not document content.  I would also argue that the text of the entity should be included in the search, but the text of the entity mentions might be redundant since that text is already in the top level fields that were processed by NLU.