On 10/3/11 6:57 PM, David Butler wrote:
Thanks Kingsley, much appreciated!Do you have any idea how soon the data is planned to be cleaned up?
The extractors need to be fixed first, then the dumps regenerated. Alternatively, the dumps can also be tweaked via text processing and transformation. Once this is done, we just load the data etc..
Thus, for now its more about fixing the dumps. Kingsley
Thanks, DavidOn Mon, Oct 3, 2011 at 1:05 PM, Kingsley Idehen <[email protected] <mailto:[email protected]>> wrote:On 10/3/11 3:28 PM, David Butler wrote:This is related to the owl:suBClassOf typo mentioned in another thread. I noticed this as well and fixed it manually in my local instance, BUT... It turns out that lots of YAGO type names are also messed up. For example: http://dbpedia.org/class/yago/ConduCtor109952539 http://dbpedia.org/class/yago/TheatricalProduCEr110705448 http://dbpedia.org/class/yago/StuDEntTeacher110666259 http://dbpedia.org/class/yago/EduCAtor110045713 http://dbpedia.org/class/yago/PrisonGuArd110149867 etc. At first I saw no pattern, but now my theory is that the type names were post-processed to capitalize common abbreviations (such as for U.S. states, countries, elements on the periodic table, and AD/BC/CE). If anyone is relying heavily on the YAGO types, they will be forced to revert back to the 3.6 version of yago_links.nt if this isn't repaired. My recommendation/request would be to fix and release a new version of this file. Thanks, David ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Dbpedia-discussion mailing list [email protected] <mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussionOnce all the brokens items are fixed, we can just reload or update the DBMS. I don't want this to happen without a serious amount of cleanups being completed first. Thus, we will need to know when all the issues have been resolved along these lines.--Regards, Kingsley Idehen President& CEO OpenLink Software Web:http://www.openlinksw.com Weblog:http://www.openlinksw.com/blog/~kidehen <http://www.openlinksw.com/blog/%7Ekidehen> Twitter/Identi.ca: kidehen ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Dbpedia-discussion mailing list [email protected] <mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
-- Regards, Kingsley Idehen President& CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca: kidehen
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________ Dbpedia-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
