Hi Cristian, I see several possible solutions:
1. The indexing tool does support LDPath. That means you can import all the required RDF files and use LDPath to append the labels of the Yago Types directly to the dbpedia entities. This would prevent additional lookups to retrieve the types, but also increase the size of the index a lot. 2. You could also index the Yago Types and use an additional Entityhub lookup to retrieve them. In this case you should first collect all types referenced by Entities in the processed text and in a second step retrieve the labels. While this means additional lookups it will only load the labels for an type once. In addition you could use a cache for types. 3. Your engine could use LDPath to retrieve the types. This would require to index the data like with option (2) and use a LDPath statement similar to (1). It would be the slowest solution (as it requires an additional lookup for every extracted entity) but require the least code. regarding: On Wed, May 7, 2014 at 9:02 AM, Cristian Petroaca <cristian.petro...@gmail.com> wrote: > I can get the labels from one of the yago downloads here : > http://www.mpi-inf.mpg.de/yago-naga/yago/download/yago/yagoMultilingualClassLabels.txt. > I'll need another yago download file to map the yago wordnet classes to > dbpedia uris. That could be done via a script maybe. I hope there is also an RDF files with that labels. In that case you need just to add it to the resource/rdfdata directory. best Rupert -- | Rupert Westenthaler rupert.westentha...@gmail.com | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen | REDLINK.CO .......................................................................... | http://redlink.co/