Show HN: We've developed a Natural Language API(dev.maluuba.com)
dev.maluuba.com
Show HN: We've developed a Natural Language API
http://dev.maluuba.com
7 comments
Would be great if this were a library that can be integrated rather than an api. An api makes things problematic because it provides the kind of functionality that would break an app if it for some reason isn't working. I don't see how it can be viable service for anything other than non-commercial/non-critical projects. Also...no php?
NLP requires a lot of computation, how fast does your API run?
It depends on the category, etc., but our own tests indicate about 100ms latency.
Wow, this is pretty cool! Could you give a few more examples to get a feel for what kind of results you get (and inputs you can give)?
Take a look at our ruby specs: https://github.com/Maluuba/napi-ruby/blob/master/maluuba_nap...
There's nearly a hundred sample sentences and expected outputs -- and they all pass :)
If you prefer other languages, we also got:
Python: https://github.com/Maluuba/napi-python/blob/master/tests/tes...
Java: https://github.com/Maluuba/napi-java/blob/master/src/test/ja...
Here is an example of a sentence and response:
>> client.interpret phrase: 'Set up a meeting with Bob tomorrow night at 7 PM to discuss the TPS reports'
response:
{:entities=> { :daterange=> [{ :start=>"2012-11-15", :end=>"2012-11-16" }], :title=> ["meeting to discuss the tps reports"], :timerange=> [{ :start=>"12:00:00AM", :end=>"12:00:00AM" }], :contacts=>[{ :name=>"bob" }] }, :action=>:CALENDAR_CREATE_EVENT, :category=>:CALENDAR }
Python: https://github.com/Maluuba/napi-python/blob/master/tests/tes...
Java: https://github.com/Maluuba/napi-java/blob/master/src/test/ja...
Here is an example of a sentence and response:
>> client.interpret phrase: 'Set up a meeting with Bob tomorrow night at 7 PM to discuss the TPS reports'
response:
{:entities=> { :daterange=> [{ :start=>"2012-11-15", :end=>"2012-11-16" }], :title=> ["meeting to discuss the tps reports"], :timerange=> [{ :start=>"12:00:00AM", :end=>"12:00:00AM" }], :contacts=>[{ :name=>"bob" }] }, :action=>:CALENDAR_CREATE_EVENT, :category=>:CALENDAR }
Cool, thank you very much!
Example URLs complain about OAuth errors. Don't provide an example if it doesn't work properly.
They do work, they just need to be authenticated with the apikey parameter -- given the experimental stage it's in, we didn't really want to publish a publicly-available key =/
Sorry for the inconvenience!
Sorry for the inconvenience!
Very cool, but I find it strange that all of the example phrases on the demo page are much longer than recommended by the API docs (<10 words). Why is this?
9 or 10 words is about the average sentence that we receive, it is just a guideline so that users understand that we aren't going to handle multiple sentences or paragraphs.
Right; the more important thing is that they all have a single intent.
I see. Thanks for your responses.
What happens when you encounter phrases with multiple intents? Is it something you can detect but is difficult to deal with, or is it a best-guess kind of thing where you attempt to obey the "first intent"? Or something else?
What happens when you encounter phrases with multiple intents? Is it something you can detect but is difficult to deal with, or is it a best-guess kind of thing where you attempt to obey the "first intent"? Or something else?