Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Natural Language First API: To Be or Not to Be

62 views

Published on

Some proponents of chatbots believe that, once we conquer natural language understanding, software systems will start communicating like humans. They say that agents will speak with other agents to get things done, with no API and no data contracts required. That remains to be seen. In the meantime, I would like to take you on a journey of building an app – not a chatbot – that was designed to use natural language as its only interface and API … well, sort of. Was it easy to build? Easy to integrate with? Did it help making the app multimodal and run on web, mobile, chat, and Alexa? I’ll answer these questions, and share lessons learned from my experiment designing and building a natural language first system.

Published in: Software
  • Be the first to comment

Natural Language First API: To Be or Not to Be

  1. 1. NATURAL LANGUAGE FIRST APIs To be, or not to be @ p v e l l e r
  2. 2. 25%
  3. 3. 50%
  4. 4. 157%
  5. 5. PAVEL VELLER CTO, DIGITAL ENGAGEMENT PRACTICE @ EPAM Systems @ P V E L L E R BLAH BLAH BLAH, NOBODY CARES… https://www.epam.com https://www.pveller.com
  6. 6. Natural Language API
  7. 7. Natural Language Understanding
  8. 8. 1. Intent Detection 2. Named Entity Recognition
  9. 9. Please schedule a meeting with Robert for tomorrow at 2pm
  10. 10. • Mark date as traveled • Mark date as not traveled
  11. 11. I will be in Stockholm on October 22th, 23th, and 24th
  12. 12. I was in SFO this past Tue and Wed
  13. 13. Assumptions
  14. 14. JSON is a text format that is completely language independent […] These properties make JSON an ideal data-interchange language.
  15. 15.  Named entity recognition is not easy  Everybody needs to do NLU for natural language APIs to take off
  16. 16. The End

×