Comments on: DBpedia Ontology – designed to break? http://blog.georgikobilarov.com/2009/11/dbpedia-ontology-designed-to-break/ Linked Data Integration Sat, 21 Aug 2010 10:09:31 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Toyhouse Memo » [Final Report] Knowledge Garden http://blog.georgikobilarov.com/2009/11/dbpedia-ontology-designed-to-break/comment-page-1/#comment-208 Toyhouse Memo » [Final Report] Knowledge Garden Thu, 14 Jan 2010 09:26:18 +0000 http://blog.georgikobilarov.com/?p=133#comment-208 [...] [4] http://blog.georgikobilarov.com/2009/11/dbpedia-ontology-designed-to-break/ [...] [...] [4] http://blog.georgikobilarov.com/2009/11/dbpedia-ontology-designed-to-break/ [...]

]]> By: François Jean http://blog.georgikobilarov.com/2009/11/dbpedia-ontology-designed-to-break/comment-page-1/#comment-41 François Jean Wed, 11 Nov 2009 13:59:16 +0000 http://blog.georgikobilarov.com/?p=133#comment-41 In my previous message, the tags were filtered-out. What I was trying to say is that before DBpedia had: http://dbpedia.org/property/presidentStart and now, it seems to only have: http://dbpedia.org/property/termStart which does not only covered the presidency start. In my previous message, the tags were filtered-out. What I was trying to say is that before DBpedia had:
http://dbpedia.org/property/presidentStart
and now, it seems to only have:
http://dbpedia.org/property/termStart
which does not only covered the presidency start.

]]> By: François Jean http://blog.georgikobilarov.com/2009/11/dbpedia-ontology-designed-to-break/comment-page-1/#comment-1189 François Jean Wed, 11 Nov 2009 13:59:00 +0000 http://blog.georgikobilarov.com/?p=133#comment-1189 In my previous message, the tags were filtered-out. What I was trying to say is that before DBpedia had: http://dbpedia.org/property/presidentStart and now, it seems to only have: http://dbpedia.org/property/termStart which does not only covered the presidency start. In my previous message, the tags were filtered-out. What I was trying to say is that before DBpedia had:
http://dbpedia.org/property/presidentStart
and now, it seems to only have:
http://dbpedia.org/property/termStart
which does not only covered the presidency start.

]]> By: François Jean http://blog.georgikobilarov.com/2009/11/dbpedia-ontology-designed-to-break/comment-page-1/#comment-37 François Jean Tue, 10 Nov 2009 22:40:06 +0000 http://blog.georgikobilarov.com/?p=133#comment-37 I was trying to run a SPARQL query on DBpedia that returns the US presidents' ages at inauguration (http://bit.ly/2zgXjJ). The queries listed there do not work anymore. In this case DBpedia seems to have lost precision in the extraction of the infoboxes. Before the tag "" was available and now it does not seem available anymore. We only have "" which is more vague because it can refer the presidency or vice-presidency function. Conclusion, the actual DBpedia, in this case, seems less precise. I was trying to run a SPARQL query on DBpedia that returns the US presidents’ ages at inauguration (http://bit.ly/2zgXjJ). The queries listed there do not work anymore. In this case DBpedia seems to have lost precision in the extraction of the infoboxes. Before the tag “” was available and now it does not seem available anymore. We only have “” which is more vague because it can refer the presidency or vice-presidency function.

Conclusion, the actual DBpedia, in this case, seems less precise.

]]> By: François Jean http://blog.georgikobilarov.com/2009/11/dbpedia-ontology-designed-to-break/comment-page-1/#comment-1188 François Jean Tue, 10 Nov 2009 22:40:00 +0000 http://blog.georgikobilarov.com/?p=133#comment-1188 I was trying to run a SPARQL query on DBpedia that returns the US presidents' ages at inauguration (http://bit.ly/2zgXjJ). The queries listed there do not work anymore. In this case DBpedia seems to have lost precision in the extraction of the infoboxes. Before the tag "" was available and now it does not seem available anymore. We only have "" which is more vague because it can refer the presidency or vice-presidency function. Conclusion, the actual DBpedia, in this case, seems less precise. I was trying to run a SPARQL query on DBpedia that returns the US presidents’ ages at inauguration (http://bit.ly/2zgXjJ). The queries listed there do not work anymore. In this case DBpedia seems to have lost precision in the extraction of the infoboxes. Before the tag “” was available and now it does not seem available anymore. We only have “” which is more vague because it can refer the presidency or vice-presidency function.

Conclusion, the actual DBpedia, in this case, seems less precise.

]]> By: Georgi http://blog.georgikobilarov.com/2009/11/dbpedia-ontology-designed-to-break/comment-page-1/#comment-34 Georgi Mon, 09 Nov 2009 11:32:02 +0000 http://blog.georgikobilarov.com/?p=133#comment-34 Leo, the dbpedia ontology isn't created automatically. it was built manually from scratch. if it would be an automatic approach i wouldn't complain, but for something that gets manually designed i think it's valid to ask for some diligence... Leo, the dbpedia ontology isn’t created automatically. it was built manually from scratch. if it would be an automatic approach i wouldn’t complain, but for something that gets manually designed i think it’s valid to ask for some diligence…

]]> By: Georgi http://blog.georgikobilarov.com/2009/11/dbpedia-ontology-designed-to-break/comment-page-1/#comment-1187 Georgi Mon, 09 Nov 2009 11:32:00 +0000 http://blog.georgikobilarov.com/?p=133#comment-1187 Leo, the dbpedia ontology isn't created automatically. it was built manually from scratch. if it would be an automatic approach i wouldn't complain, but for something that gets manually designed i think it's valid to ask for some diligence... Leo, the dbpedia ontology isn’t created automatically. it was built manually from scratch. if it would be an automatic approach i wouldn’t complain, but for something that gets manually designed i think it’s valid to ask for some diligence…

]]> By: Georgi http://blog.georgikobilarov.com/2009/11/dbpedia-ontology-designed-to-break/comment-page-1/#comment-33 Georgi Mon, 09 Nov 2009 11:29:02 +0000 http://blog.georgikobilarov.com/?p=133#comment-33 Anja, the thing is that in my opinion the old ontology schema should be fixed. instead, you introduce a new one that not only doesn't fix the problem but creates new problems. Anja, the thing is that in my opinion the old ontology schema should be fixed. instead, you introduce a new one that not only doesn’t fix the problem but creates new problems.

]]> By: Georgi http://blog.georgikobilarov.com/2009/11/dbpedia-ontology-designed-to-break/comment-page-1/#comment-1186 Georgi Mon, 09 Nov 2009 11:29:00 +0000 http://blog.georgikobilarov.com/?p=133#comment-1186 Anja, the thing is that in my opinion the old ontology schema should be fixed. instead, you introduce a new one that not only doesn't fix the problem but creates new problems. Anja, the thing is that in my opinion the old ontology schema should be fixed. instead, you introduce a new one that not only doesn’t fix the problem but creates new problems.

]]> By: Leo Sauermann http://blog.georgikobilarov.com/2009/11/dbpedia-ontology-designed-to-break/comment-page-1/#comment-28 Leo Sauermann Sat, 07 Nov 2009 09:55:16 +0000 http://blog.georgikobilarov.com/?p=133#comment-28 With a wild, evolving datasource like wikipedia, a fine-grained approach such as this sounds not tooooo bad. Its a tradeoff, we can't manually create the ontology, but have to create it vastly automated based on the infoboxes. In my opinion, the key would be to do analysis and data quality on top, like YAGO does. But besides my own view, I trust Bernhard on his judgement. With a wild, evolving datasource like wikipedia, a fine-grained approach such as this sounds not tooooo bad. Its a tradeoff, we can’t manually create the ontology, but have to create it vastly automated based on the infoboxes. In my opinion, the key would be to do analysis and data quality on top, like YAGO does. But besides my own view, I trust Bernhard on his judgement.

]]>