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.

Ability to configure one entity as a synonym for another entity

This will enable configuring WA entities with less effort. There are scenarios where one entity and all its synonyms can be applied to another entity with additional synonyms (Mostly in a hierarchical entity model). As of now we have to manually configure all the synonyms from one into another

  • Jun 18 2018
  • Future Consideration
Why is it useful?
Who would benefit from this IDEA? Customer
How should it work?
Idea Priority
Priority Justification
Customer Name
Submitting Organization
Submitter Tags
  • Attach files
  • Admin
    Mitch Mason commented
    07 Jan 21:42

    Can you give some examples where this is useful?

  • Chris Ratcliffe commented
    26 Mar 19:00

    I can't speak for the OP, but if this request is what I think it is, here is how I would use hierarchical entities. 

    Entity: classic_computers

    • Value: apple  synonyms: apple 2e, apple 2gs, apple 2c
    • Value: amiga
    • Value: IBM  synomys: PC XT, PC AT

    Entity: modern_computers

    • Value: hp
    • Value: dell
    • value: lenovo
    • value: macbook

    Entity: all_computers

    • Value: Entity:classic_computers
    • Value: Entity:modern_computers


    An utterance like lenovo would trigger both the modern_computers and all_computers entity, and the literal would be lenovo in both situations.  Possibly, the entity could have a new attribute like nested or something that could be true if the literal that triggered the entity was from a hierarchical reference, but that would not be critical.