Hi Jan!

Yes, you are right (my example was bad regarding P31 instance of; I should have found a better example).  But I think Cord understood the idea I was trying to explain.
Your warning of using P31 correctly stems from the current constraints on P31, which are fairly clear, here's a few of them:

Multiple P31 claims lead to duplicate tuples
Avoid P31 of P279 of Q5 (P106 or other properties should be created)
Can't be instance of both human and occupation

and tons of other usage and constraint rules on P31 to help keep things tidy and clean in Wikidata.



On Fri, Oct 9, 2020 at 5:43 PM Jan Ainali <ainali.jan@gmail.com> wrote:
Den fre 9 okt. 2020 kl 21:41 skrev Thad Guidry <thadguidry@gmail.com>:

It's always best to look at the properties for this type P1963 on any particular entity type, such as looking and scrolling down on Q5 human or Q901 scientist which already lists many of those properties above.  Whatever is in properties for this type is further used as a dropdown statement hint and its based on if you apply a instance of statement and fill in a more specific type for a person, like saying this person is an instance of chess player, or scientist, or politician.


No, don't add occupations as P31 on humans. Add them with P106 instead.

/Jan
_______________________________________________
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata