| This is cool! We've been working on something similar, but the opposite direction (for world trade data). Instead of trying to NLP our way out of the problem, we pre-generate and index a bunch of possible questions, and let full text search handle the rest. It's interesting, because theoretically NLP should be able to "understand" what you mean but in reality I find that even if you parse sentence structure and extract some meaning, you're still at some level hardcoding the possible things that can be queried into the code. So it's a neat tradeoff of whether it's more worth it to create a mini query language, or go full natural language, or go somewhere in between. ... Anyway, try it out by clicking on the title (keeping it a bit hidden for now for testing purposes): http://atlas.cid.harvard.edu/explore/tree_map/export/usa/all... Things you can try (mix and match too!): - "wine italy"
- "france"
- "germany spain"
- "germany export wine 2002 to 2012"
- "turkey feasible" ... If you want to see the code, check out our github: https://github.com/cid-harvard/atlas-economic-complexity/blo... (search view) https://github.com/cid-harvard/atlas-economic-complexity/blo... (indexer) Apologies for any mess, I recently joined and we're undergoing a huge overhaul right now. |
a. have structured queries that can be precisely parsed
b. provide query completion to guide the user while entering the query
It turned out quite well, if I say so myself. But I never got the time to market it.
It can be seen in action here: http://nlq.lavadip.com/servlet/demo