Hello,
Kingsley Idehen wrote:
Jens Lehmann wrote:
We are completing a similar test here based on my response earlier this
week.
Was the test successful?
I assume you are trying to load the Yago Class Hierarchy? If so, let us
finish our investigation and then we will have a proper
Kingsley,
Thanks for doing this: I'll have a play next week when I have a bit more
time.
I notice that you have set up the variants as sub-properties, rather
than say owl:sameAs. Does this imply that we have, in effect, one
preferred term and N non-preferred terms for each property? If so,
Jens Lehmann wrote:
Hi Kingsley,
Kingsley Idehen wrote:
Note that Virtuoso does support inferencing for subclass and
subproperty.
The issue here is that no inferencing rules have been requested or
created during the various data loads into Virtuoso.
See:
Richard Cyganiak wrote:
On 16 May 2008, at 22:06, Richard Light wrote:
1. Find the class(es) used in DBpedia of that kind of thing. For
example, if
you look at a couple of persons, you will find that they usually
have the
classes yago:Person17846 and foaf:Person. Classes in
Yes, this could be done. The problem is that Wikipedia is huge, and
there are tens of thousands of properties covering all sorts of
domain. Hence we would need either an automated approach to find those
duplicated properties, or lots of volunteers who go through the
dataset and find them
Richard,
On 16 May 2008, at 14:16, Richard Light wrote:
That is, that dates of birth and death
appear as different properties:
p:birthplace
p:birthPlace
p:cityofbirth
etc.
I can see how this diversity arises, due to the harvesting approach
used. However, (and I'm probably showing my
I'm working on a project that's trying to use data from dbpedia to
disambiguate references to people in text. One thing we are trying to
figure out is the use of several properties to encode the same
attribute. For example, we found that the following dbpedia
properties are all used for a
