6 ms·
I've actually built this exact thing (it was for a question-answering over linked data thing). It worked, sort of. But only after I mapped the many different r
by nl 9y ago
I've actually built this exact thing (it was for a question-answering over linked data thing).
It worked, sort of. But only after I mapped the many different representations of "age" used by the different end points.
I don't remember the specifics, but even in DBPedia alone you have to deal with the properties and the ontology namespace. Then YAGO uses that but brings in other sources and puts them in their own fields. Freebase does (did) its own things.. etc etc.
It was a long, long way from the "you don't need to know anything" utopia you describe.
In summary, there really is no advantage over mapping from a REST endpoint.
Plus, the database endpoints are slow (and even worst - have high variance in performance). I ended up downloading the dumps and hosting them all myself because the servers were so slow and unreliable.