Property talk:P10663

Documentation

• Start a query
• Properties using this qualifier (statistics)
• Count

applies to work
work or narration for or in which this statement is true

Data type	Item
Domain	fictional entity (Q14897293)
Example	Gawain (Q831685) → Wigalois (Q2569730) The Little Man (Q5787753) → The Pink Panther Show (Q140680) Mahogany Town (Q15133086) → Pokémon HeartGold and SoulSilver (Q611189)
See also	present in work (P1441), applies to part (P518), of (P642), in work (P2553)
Lists	Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P10663
Proposal discussion	Proposal discussion
Current uses	Total 24,046 Qualifier 24,036 >99.9% of uses Reference 10 <0.1% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Type “fictional entity (Q14897293)”: item must contain property “instance of (P31), subclass of (P279)” with classes “fictional entity (Q14897293)” or their subclasses (defined using subclass of (P279)). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10663#Type Q14897293, SPARQL

Scope is as qualifier (Q54828449): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10663#Scope, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10663#Entity types

Conflicts with “instance of (P31): human (Q5)”: this property must not be used with the listed properties and values. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10663#Conflicts with P31, search, SPARQL

Value type “work (Q386724), series of creative works (Q7725310), mythology (Q9134), group of works often treated as a singular work (Q116779428)”: This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value work (Q386724), series of creative works (Q7725310), mythology (Q9134), group of works often treated as a singular work (Q116779428) (or a subclass thereof). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10663#Value type Q386724, Q7725310, Q9134, Q116779428, SPARQL

Is this correct usage? @Valentina.Anitnelav: --Trade (talk) 13:23, 13 May 2022 (UTC)

@Trade:, yes, I added it as an allowed qualifier - Valentina.Anitnelav (talk) 13:37, 13 May 2022 (UTC)

Shouldn't P1441/P642 be removed as allowed qualifiers or otherwise replaced through a batch? @Valentina.Anitnelav: --Trade (talk) 13:41, 13 May 2022 (UTC)

Feel the same about used by (P1535), wears (P3828), performer (P175), hairstyle / hairlength (P8839), occupation (P106), residence (P551) and significant event (P793)? I have noticed that fictional characters using these were not caught by your batch. --Trade (talk) 13:51, 13 May 2022 (UTC)

@Trade: I agree completely. I'm not finished, yet :). At the moment I'm moving qualifiers used for the property performer (P175). - Valentina.Anitnelav (talk) 13:58, 13 May 2022 (UTC)