W3C home > Mailing lists > Public > public-lod@w3.org > August 2009

Re: [Dbpedia-discussion] Fwd: Your message to Dbpedia-discussion awaits moderator approval

From: Tim Finin <finin@cs.umbc.edu>
Date: Mon, 10 Aug 2009 16:27:17 -0400
Message-ID: <4A8082A5.1000306@cs.umbc.edu>
To: Kavitha Srinivas <ksrinivs@gmail.com>
CC: Kingsley Idehen <kidehen@openlinksw.com>, Anja Jentzsch <anja@anjeve.de>, "public-lod@w3.org" <public-lod@w3.org>, dbpedia-discussion@lists.sourceforge.net
Kavitha Srinivas wrote:
> I understand what you are saying -- but some of this reflects the way
> types are associated with freebase instances.  The types are more like
> 'tags' in the sense that there is no hierarchy, but each instance is
> annotated with multiple types.  So an artist would in fact be annotated
> with person reliably (and probably less consistently with
> /music/artist).  Similar issues with Uyhurs, murdered children etc.  The
> issue is differences in modeling granularity as well.  Perhaps a better
> thing to look at are types where the YAGO types map to Wordnet (this is
> usually at a coarser level of granularity).

I think you need a different property to express the relation between the
freebase types and yago classes.  The whole point of grounding OWL in logic is
to allow people and computers to draw inferences from the OWL statements.  Those
statements in the dump do assert that anything that is in the set yago:Uyghurs
is also in the set yago:MurderedChildren and vice versa.

Why not use rdfs:subClassOf to relate a yago class to a freebase type when every
member of the class is tagged with the type but not everything tagged with the
type is a member of the class.

skos:narrower is another option, maybe.
Received on Monday, 10 August 2009 20:28:20 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:22 UTC