Dimitris Kontokostas

Not 100% sure but maybe you need to run the settings re-generation to get this fixed, iirc this updates all the Wikipedia related configuration see https://github.com/dbpedia/extraction-framework/wiki/Extraction-Instructions#generate-settings

We already implemented something similar to (1) for separate templates maybe it makes sense to do it for nested too. I don't think it will break something but not 100%...

I think we should try #4

This is the default behavior to avoid multiple property definitions. Here is the code that cleans the URIs: https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/InfoboxExtractor.scala#L278-290

This does not affect the mappings extractor & intermediate nodes, only the raw infobox extractor data. In some cases it might make sense to keep the numbers but there are...

Vladimir, please do not use the custom extractor when testing, this produces data from all available extractors (even infobox extractor) use the default option that extracts only labels and mappings...

> @jimkont https://github.com/jimkont "please do not use the custom > extractor when testing, this produces data from all available extractors > (even infobox extractor)": is there any harm in that?...

for Jesus, [in the revision we parsed](https://en.wikipedia.org/wiki/Jesus?oldid=645813283), the date is taken from the persondata template. The data from the infobox says 'birth_date = 7–2 BC' which we failed to parse...

actually, `dbpedia.org` is the exception to all rules since I18n was actively enabled :) the same way we have `fr.dbpedia.org` from `fr.wikipedia.org` we should also have `en.dbpedia.org` but it was...

this is a different issue. @pkleef is this related to the new 2015-10 version? I see the data are not yet deployed in dbpedia.org but maybe the code from the...