Property talk:P12641
Jump to navigation
Jump to search
Documentation
Duden sense ID
A URL slug of a sense in duden.de
A URL slug of a sense in duden.de
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “polysemous word (Q125397971)”: item must contain property “instance of (P31), subclass of (P279)” with classes “polysemous word (Q125397971)” or their subclasses (defined using subclass of (P279)). (Help)
List of violations of this constraint: Database reports/Constraint violations/P12641#Type Q125397971, hourly updated report, SPARQL
Scope is as main value (Q54828448), as reference (Q54828450): 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/P12641#Scope, SPARQL
Format “
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). [a-zA-Z0-9_]+#Bedeutung-\d+(\w)?”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P12641#Format, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of violations of this constraint: Database reports/Constraint violations/P12641#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
Allowed entity types are Wikibase sense (Q54285715): 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/P12641#Entity types
Lexeme language: German (Q188): this property should only be applied to lexemes with these languages (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/P12641#language
Constraints[edit]
As @Shisma pointed out, there is a subject type constraint defined for this property,but the constraint is meant to be applied to the parent lexeme of the sense, not to the sense this property pertains to) iI hope @Shisma can explain this better than me, preferrably with some examples of constraint violations.--̴̴ SM5POR (talk) 15:20, 19 April 2024 (UTC)
- I don't know if there is a appropreate constraint type for such a situation, that's why I asked at the Wikidata talk:WikiProject property constraints. I suppose we should just remove the constraint for the time being –Shisma (talk) 11:48, 20 April 2024 (UTC)
- Hello Shisma
Notified participants of WikiProject property constraints,
I'm not sure if I understand the problem correctly and hope to help with this post. If a property must be added to a Lexeme, but it necessarily concerns a Sense, subject sense (P6072) must be added using required qualifier constraint (Q21510856) to the property. subject type constraint (Q21503250) can be kept with this other constraint. Have I correctly identified the problem? Cordially. ―Eihel (talk) 00:09, 21 April 2024 (UTC)- @Shisma@ZI Jonyː Do I understand it correctly that this property must not be applied to the sense of a lexeme in a language other than German? And, does the required qualifier constraint suggested by @Eihel solve the problem. I'm sorry if I moved the question to an inappropriate page prematurely even if there isn't a usable constraint type already, but as it currently concerns this property alone, I don't see why the discussion couldn't start here and perhaps could be referred elsewhere if and when the need for that arises. --̃ ̃~̃ ̃ ̃ SM5POR (talk) 12:22, 21 April 2024 (UTC)
- As I understand, sense of lexeme doesn't apply other than German. And, Eihel's suggestion may solve the problem. IMO, subject type constraint (Q21503250) should be removed, and add required qualifier constraint (Q21510856) → part of (P361) → polysemous word (Q125397971), subject sense (P6072) will not work here well, also add allowed qualifiers constraint (Q21510851). I'd suggest not to add instance of (P31) for each sense, like added Schere (L7627-S3), Batterie (L222595-S4). Regards, ZI Jony (Talk) 18:50, 21 April 2024 (UTC)
- But a sense is not a word. a lexeme is – Shisma (talk) 12:02, 30 April 2024 (UTC)
- As I understand, sense of lexeme doesn't apply other than German. And, Eihel's suggestion may solve the problem. IMO, subject type constraint (Q21503250) should be removed, and add required qualifier constraint (Q21510856) → part of (P361) → polysemous word (Q125397971), subject sense (P6072) will not work here well, also add allowed qualifiers constraint (Q21510851). I'd suggest not to add instance of (P31) for each sense, like added Schere (L7627-S3), Batterie (L222595-S4). Regards, ZI Jony (Talk) 18:50, 21 April 2024 (UTC)
- @Shisma@ZI Jonyː Do I understand it correctly that this property must not be applied to the sense of a lexeme in a language other than German? And, does the required qualifier constraint suggested by @Eihel solve the problem. I'm sorry if I moved the question to an inappropriate page prematurely even if there isn't a usable constraint type already, but as it currently concerns this property alone, I don't see why the discussion couldn't start here and perhaps could be referred elsewhere if and when the need for that arises. --̃ ̃~̃ ̃ ̃ SM5POR (talk) 12:22, 21 April 2024 (UTC)
- Hello Shisma
Categories:
- D-A-CH-related properties
- All Properties
- Properties with external-id-datatype
- Properties used on 10+ items
- Properties with constraints on type
- Properties with scope constraints
- Properties with format constraints
- Properties with unique value constraints
- Properties with entity type constraints
- Properties with lexeme language constraints