Re:Wolfram Alpha’s New Data about Pokémon
by taliesinb on Thursday October 17, 2013 @01:13AM
(#6563796)
Some of our stuff is simple database lookup (ala Google knowledge graph), other stuff is more algorithmic and computational in nature.
The problem we've had with SPARQL and co is that we feel it isn't optimized for computational queries. Ontologies don't matter as much in that case, and inference in tuple stores costs you significantly in performance, although the technology is improving.
As often as not, however, the computationally irreducible work lies in making a domain suitable for computational consumption, not in the technology used for representation.
To analogize, UTF-8 is great, but without the notion of Unicode code points it wouldn't exist.
that said it's within grasp of many of us: natural language interfaces (NLI) and SPARQL databases and endpoints. have a look at this semanticweb q&a:
http://answers.semanticweb.com/questions/12747/natural-langu...
some good links in there. basically find your SPARQL endpoints, have a list of synonyms mapped between your inputs (which you parse with NLP tools like weka or the stanford parser, or even python's nltk) and map your query to your ontologie(s) from your endpoints. then try successive answers.
a good, simple interface to play around with that is quepy:
http://quepy.machinalis.com/
a few others exist.
hope that helps. despite challenges in the adoption rates of the semantic web, i think it's the future of information retrieval because it makes sense for us as users and truly organizes information.