I like very much the "contributing back" aspect of this. Thanks for
offering! One problem is that some pages have no template, making it
impossible to use the template-type mappings defined on the mappings wiki.

Other people have implemented type inferencing from categories, lists and
even from the text.

Others, by cross-referencing with Freebase, Cyc, etc.

I am wondering if the type statements obtained through all these approaches
should not be imported back to DBpedia through some semiautomatic curation
method (read mappings wiki beyond templates).

I guess we could also use the wiki, and allow people to also add mappings
for Lists, Categories, Tables, and other features generated by these
approaches?

Cheers
Pablo
On Apr 9, 2014 2:29 PM, "Kingsley Idehen" <kide...@openlinksw.com> wrote:

> On 4/9/14 4:53 PM, Paul Houle wrote:
>
>>   The type assignments in DBpedia are very precise (few false
>> statements) but not accurate in the sense that recall is poor;  many
>> things fall through the cracks.  The real problem is that the the
>> mappings are the map,  not the territory.  Wikipedia is an
>> encyclopedia for humans,  not for machines,  so DBpedia has to parse
>> whatever unsane markup they give us.
>>
>>   Systems like Wikidata and Freebase can be edited by machines and
>> human ontologists and get better recall for types.
>>
>> http://basekb.com/
>>
>>    is a conversion from Freebase to industry standard RDF.  You could
>> use :BaseKB as a substitute for DBpedia,  but DBpedia has advantages
>> too because in addition to the 4 million things important enough to be
>> in DBpedia,  there is another 37 million unimportant things in :BaseKB
>> that matter only to librarians,  video store clerks and professional
>> discographers.
>>
>>    These unimportant things will drive you crazy unless you master
>> them,  and the easiest way to turn down the noise is to restrict
>> search to the 4 million things.
>>
>>    I could make you an RDF file that has statements such as
>>
>> ?dbpediaTopic a ?freebaseType .
>>
>>    you could load that together with the rest of DBpedia.  That would
>> get you a long way towards good lists.  The trouble at this point is
>> that you don't have the freebase types connected to the DBpedia types
>> so you can't join them against the schema to find properties and such.
>>   Mapping the types to the DBpedia types would not be that hard either,
>>   since the two systems are well aligned.  Then you get something that
>> looks like DBpedia but has more accurate types.
>>
>>     Freebase has more accurate and better populated data for things
>> like ticker symbols,  geo-coordinates,  genders,  birth dates and the
>> like.  It would not be hard to rewrite Freebase statements to
>>
>> ?dbpediaTopic ?freebasePredicate ?anotherDbpediaTopic .
>>
>>    and that would produce something that would be remarkably user
>> friendly.
>>
>
> :baseKB could (and maybe should) pitched as a human-and-machine curated
> bridge between Freebase, DBpedia, and Wikidata (I think).
>
> Have you considered mapping the classes and properties across DBpedia,
> Freebase, and Wikidata?
>
>
> --
>
> Regards,
>
> Kingsley Idehen
> Founder & CEO
> OpenLink Software
> Company Web: http://www.openlinksw.com
> Personal Weblog: http://www.openlinksw.com/blog/~kidehen
> Twitter Profile: https://twitter.com/kidehen
> Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
> LinkedIn Profile: http://www.linkedin.com/in/kidehen
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Dbpedia-discussion mailing list
> Dbpedia-discussion@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
>
>
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Dbpedia-discussion mailing list
Dbpedia-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion

Reply via email to