The Wikidata subclass of ontology/taxonomy is unfortunately a lot of
true-but-unhelpful info if you do some inferencing.
Subclassing in particular is not very useful. As an example, let's take the
Mayor of Madison, WI - for any property we say about her, what are the
classes and superclasses of the target of that, e.g. we say that she's a
Mayor, what classes are 'Mayor' a member of?
SELECT distinct ?p ?pLabel ?item ?itemLabel ?itemClass ?itemClassLabel
WHERE
{
wd:Q63039729 ?p ?item. # Q63039729 is the current mayor of madison
OPTIONAL {?item wdt:P31/wdt:P279* ?itemClass . }
SERVICE wikibase:label { bd:serviceParam wikibase:language
"[AUTO_LANGUAGE],en". } # Helps get the label in your language, if not,
then en language
} order by (?item)
This query comes back with 562 classes, most of which are upper-ontology
statements that are really not very useful at best and in some cases almost
feel like they're so irrelevant as to make the whole exercise pointless -
for example,
- via some subclass path in wikidata, we learn that 'United States of
America' is a member of the classes 'agent', 'matter', 'set', and
'astronomical body part'.
- The Mayor's first name is 'Satya', which is a member of the classes
'data', 'information', 'series', 'non-physical entity', 'multiset', and a
'mathematical object', among others.
- She was educated at 'Smith College', which (I'm happy to learn from
wikidata) is a member of the class '3 dimensional objects'.
- The mayor is the first gay mayor of Madison, and it turns out
according to wikidata 'lesbianism' is a member of the class 'occurence',
'spatio-temporal entity', and more.
So while I guess an auxiliary database with inferences from wikidata would
be neat, I think it'd be a lot of noise and I'm not sure all that useful in
practice.
I do wish that there was some support in wikibase to know more about
classes and instances - so if you add a P31 instanceOf property to an item
or a P279 subClassOf to a class, Wikibase tells you "BTW, you're also
saying that your thing is also an instance of all of these classes/your
class is now a subclass of all these other classes too"
-Erik
On Fri, Dec 23, 2022 at 3:46 PM Dan Brickley <[email protected]> wrote:
>
>
> On Fri, 23 Dec 2022 at 21:32, Peter F. Patel-Schneider <
> [email protected]> wrote:
>
>> Why should this not be done? It seems reasonable to me. Is there some
>> official statement that this should not be done?
>>
>
> The Blazegraph Wikidata SPARQL endpoint (as it is a sadly abandoned
> codebase) already creaking at the seams, and struggling to keep up with the
> happily thriving growth of Wikidata.
>
> In this situation it seems that adding redundant factoids into the
> database might not be the best use of constrained resources, for now at
> least.
>
> More generally, where is any notion of inference in Wikidata defined?
>>
>
> This is a good question, I’d love to know too. Maybe mapping the
> equivalent P:Whatevers to rdfs:subClassOf and rdf:type would be a start?
>
> If they were in a form from which we could generate even just SPARQL
> CONSTRUCT queries, and perhaps populate an auxiliary dataset/database with
> the additional implied information.
>
> Dan
>
>> There appear to be more problems with sports season. For example,
>> https://www.wikidata.org/wiki/Q1487136 doesn't appear to be linked to
>> any league or cup.
>>
>>
>>
>>
>> peter
>>
>>
>> On 12/23/22 15:15, Thad Guidry wrote:
>>
>>
>> Please do not do this,
>> What you are likely wanting to accomplish is relating a sports season to
>> a category of sports and this is already done. So the relationships are
>> inferred.
>>
>> On Fri, Dec 23, 2022 at 11:01 PM Romaine Wiki <[email protected]>
>> wrote:
>>
>>> Hi all,
>>>
>>> Too many items on Wikidata still miss the basic statements. Perhaps we
>>> can focus together for a short period of time on a single subject to get
>>> this fixed.
>>>
>>> For example: all items with instance of (P31) sports season should also
>>> have have sport (P641) as statement.
>>>
>>> When I just ran a query I saw 24000 sports season items that are still
>>> missing sport (P641).
>>>
>>> Query:
>>> https://query.wikidata.org/#SELECT%20%3Fitem%20%3FitemLabel%20WHERE%20%7B%0A%20%20%3Fitem%20wdt%3AP31%20wd%3AQ27020041%20.%0A%20%20MINUS%20%7B%0A%20%20%20%20%3Fitem%20wdt%3AP641%20%3Fmissing%20.%0A%20%20%7D%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%22.%20%7D%0A%7D%0A
>>>
>>> I already did a few myself but for the largest part help is needed. Who
>>> has ideas and can help getting this statement added to all the sports
>>> season items.
>>>
>>> Thanks!
>>>
>>> Romaine
>>>
>>> _______________________________________________
>>> Wikidata mailing list -- [email protected]
>>> Public archives at
>>> https://lists.wikimedia.org/hyperkitty/list/[email protected]/message/GST2SPL43JUGN74242BWRS7CYDLFMDCL/
>>> To unsubscribe send an email to [email protected]
>>>
>> --
>> Thad
>> https://www.linkedin.com/in/thadguidry/
>> https://calendly.com/thadguidry/
>>
>> _______________________________________________
>> Wikidata mailing list -- [email protected]
>> Public archives at
>> https://lists.wikimedia.org/hyperkitty/list/[email protected]/message/ERKXD6D3673T6GA5NGBAYTAW44DDHTPY/
>> To unsubscribe send an email to [email protected]
>>
>> _______________________________________________
>> Wikidata mailing list -- [email protected]
>> Public archives at
>> https://lists.wikimedia.org/hyperkitty/list/[email protected]/message/OD5VGSCX2JF6QXXLBDMJCEZMN6OPOFY4/
>> To unsubscribe send an email to [email protected]
>>
> _______________________________________________
> Wikidata mailing list -- [email protected]
> Public archives at
> https://lists.wikimedia.org/hyperkitty/list/[email protected]/message/VEE75U26Y7UR2WA5XQHYXLMB7CWEMMOJ/
> To unsubscribe send an email to [email protected]
>
_______________________________________________
Wikidata mailing list -- [email protected]
Public archives at
https://lists.wikimedia.org/hyperkitty/list/[email protected]/message/KQIWTMBKWXWX5RTBEJ3PCPOYQSUO3VKS/
To unsubscribe send an email to [email protected]
