Hello,
Richard Light schrieb:
>
> OK: attached is a text document containing what I think are 49
> correctly-framed declarations of equivalence and sub-property-ness for
> various birth and death date and place properties.
We added a simple ini file for different spelling of the same property
i
Jens Lehmann wrote:
>
> 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 inves
Richard Light wrote:
>
> 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.
Correct.
> Does this imply that we have, in effect, one "preferred term" and N
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
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 pro
Richard Light wrote:
> In message <[EMAIL PROTECTED]>, Kingsley Idehen
> <[EMAIL PROTECTED]> writes
>>
>> We can inference over rules for classes and subclasses.
>
> Sounds good.
>
>> I'll look at what you've sent when I have a moment. If you've sent
>> triples then we can create rules etc.. If
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: http://docs.o
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: http://docs.openlinksw.com/virtuoso/rdfsparqlru
Richard Light wrote:
> In message <[EMAIL PROTECTED]>, Kingsley Idehen
> <[EMAIL PROTECTED]> writes
>>
>> We can inference over rules for classes and subclasses.
>
> Sounds good.
Meant to say subclasses & subproperties.
>
>> I'll look at what you've sent when I have a moment. If you've sent
>> tr
In message <[EMAIL PROTECTED]>, Kingsley Idehen
<[EMAIL PROTECTED]> writes
>
>We can inference over rules for classes and subclasses.
Sounds good.
>I'll look at what you've sent when I have a moment. If you've sent
>triples then we can create rules etc.. If all is done right we might
>even ma
Richard Light wrote:
>
> OK: attached is a text document containing what I think are 49
> correctly-framed declarations of equivalence and sub-property-ness for
> various birth and death date and place properties.
>
> Are the equivalences the most helpful way round? (The "standard"
> property i
OK: attached is a text document containing what I think are 49
correctly-framed declarations of equivalence and sub-property-ness for
various birth and death date and place properties.
Are the equivalences the most helpful way round? (The "standard"
property is on the right of the expressio
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
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 DBpedia are
>> quite
>
>You can get an idea of the properties used for a particular kind of resource
>by following these steps:
>
>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
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, (an
>> 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
In message <[EMAIL PROTECTED]>, Richard
Cyganiak <[EMAIL PROTECTED]> writes
>>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. Ho
Richard,
On 15 May 2008, at 16:46, Richard Light wrote:
> Just joined this list, and noticed a post from Tim Finin, who asked
> exactly the question that occurred to me on browsing through a typical
> dbPedia page (for Edinburgh). That is, that dates of birth and death
> appear as different prope
Hi,
Just joined this list, and noticed a post from Tim Finin, who asked
exactly the question that occurred to me on browsing through a typical
dbPedia page (for Edinburgh). That is, that dates of birth and death
appear as different properties:
p:birthplace
p:birthPlace
p:cityofbirth
etc.
I
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 person'
21 matches
Mail list logo