Property talk:P461

From Wikidata
Jump to navigation Jump to search

Documentation

opposite of
item that is in some way the opposite of this item
Descriptionitem that is the opposite of this item. See also: different from (P1889)
Representsopposite (Q1498321), antonym (Q131779)
Data typeItem
Domainabstract terms (note: this should be moved to the property statements)
Allowed valuessimilar (probably bidirectional) (note: this should be moved to the property statements)
Usage notesOnly use with values that are directly opposed to the item with respect to a binary quality or relation. If the quality or relation is not binary, use P1889.
Examplewar (Q198) → peace (Q454)
proprietary software (Q218616) → free software (Q341)
winter (Q1311) → summer (Q1313)
black (Q23445) → white (Q23444)
south (Q667) → north (Q659)
female (Q6581072) → male (Q6581097)
Robot and gadget jobsthe property is supposedly bidirectional
Tracking: usageCategory:Pages using Wikidata property P461 (Q27949513)
See alsoinverse property (P1696), criterion used (P1013), different from (P1889), said to be the same as (P460), antonym (P5974), synonym (P5973)
Lists
Proposal discussionProposal discussion
Current uses
Total39,852
Main statement39,839>99.9% of uses
Qualifier12<0.1% of uses
Reference1<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Symmetric property: if [item A] has this property linked to [item B], then [item B] should also have this property linked to [item A]. (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/P461#Symmetric, SPARQL
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: nationalism (Q6235), cosmopolitanism (Q188843), universalism (Q6843150), provincialism (Q1733479), parochialism (Q30323949), naturalization (Q841440)
List of violations of this constraint: Database reports/Constraint violations/P461#Single value, 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/P461#Entity types
Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410)”: this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P461#Conflicts with P31, hourly updated report, search, SPARQL
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P461#Scope, hourly updated report, SPARQL
Single-value constraint with class exceptions
Modification of the single-value constraint allowing multiple values on items belonging to class point of view (Q12558574), belief system (Q5390013), mental state (Q54989186), or social movement (Q49773). (Help)
Violations query: SELECT DISTINCT ?item ?itemLabel ?count ?sample1 ?sample1Label ?sample2 ?sample2Label WHERE { VALUES ?goodClass { wd:Q12558574 wd:Q5390013 wd:Q54989186 wd:Q49773 }. { SELECT ?item (COUNT(?value) AS ?count) (MIN(?value) AS ?sample1) (MAX(?value) AS ?sample2) { ?item p:P461 [ ps:P461 ?value; wikibase:rank ?rank ] . FILTER( NOT EXISTS {?item wdt:P31/wdt:P279* ?goodClass} ) . FILTER( ?rank != wikibase:DeprecatedRank ) . } GROUP BY ?item HAVING ( ?count > 1 ) } . SERVICE wikibase:label { bd:serviceParam wikibase:language "en" } . } ORDER BY DESC(?count)
List of this constraint violations: Database reports/Complex constraint violations/P461#Single-value constraint with class exceptions

Test[edit]

Which qualifier to use? → Wikidata:Property_proposal/Archive/35#frame_of_reference_for_opposition

Films shot in vs Films set in[edit]

Are they really opposite? --AVRS (talk) 21:21, 6 September 2015 (UTC)[reply]

One is the location, the other the location that is being represented. If it's a problem, it we could use different from (P1889) instead. --- Jura 06:28, 9 September 2015 (UTC)[reply]

Inverse function[edit]

This property is also used to indicate the inverse function (list of such usages). Creating a dedicated property for this purpose should be considered. Petr Matas 14:47, 22 December 2015 (UTC)[reply]

The query was wrong, but it's fixed now. Petr Matas 14:53, 22 December 2015 (UTC)[reply]
I think the qualifier should be criterion used (P1013): inverse function (Q191884). Petr Matas 16:31, 22 December 2015 (UTC)[reply]

Q7521081[edit]

@Jura1: If this property is also applied to identical names? See for example Q7521081. --Harry Canyon (talk) 09:03, 3 April 2016 (UTC)[reply]

@Harry Canyon: There is given name version for other gender (P1560). --AVRS (talk) 09:53, 3 April 2016 (UTC)[reply]

@AVRS: OK, then I will remove it from Q7521081. --Harry Canyon (talk) 09:58, 3 April 2016 (UTC)[reply]

@Harry Canyon: P1560 is for given names in the same language. P461 is used when merely the spelling is identical.
--- Jura 05:45, 11 June 2016 (UTC)[reply]

Should setup a pywikibot script[edit]

To change usage of this property on Property: namespace, when possible, to inverse property (P1696) with same value(s). --Liuxinyu970226 (talk) 15:05, 29 December 2017 (UTC)[reply]

This property has wikibase-item datatype, it cannot link to properties. Matěj Suchánek (talk) 10:25, 7 January 2018 (UTC)[reply]

just added statement is subject of (P805) to allowed qualifiers[edit]

this should help us link dichotomies to items discussing them. Arlo Barnes (talk) 03:29, 7 June 2020 (UTC)[reply]

is this property suitable for embassies?[edit]

embassy country A in country B opposite of (P461) ==> embassy country B in country A ? Bouzinac 💬●✒️●💛 15:18, 17 September 2020 (UTC)[reply]

@Bouzinac: Some embassies have this property but I'm not sure it's always suitable as it's not a bijective relation. For example, what is the opposite of (P461) of Embassy of France, Suva (Q2841703) ? It should be Embassy of Fiji to Belgium (Q25047637) as this embassy is accredited to France: it is a little bit weird... And the opposite of (P461) of Embassy of Fiji to Belgium (Q25047637) should be Embassy of Belgium, Canberra (Q104523186) as there is no embassy of Belgium in Fiji. At the end we should consider that Embassy of France, Suva (Q2841703) is the equivalent of Embassy of Belgium, Canberra (Q104523186) which is a total nonsense. Pymouss (talk) 11:20, 4 April 2021 (UTC)[reply]
Hi Pymouss, understood your example A>>A'>>B'>>B but not A>>B. I was mostly thinking about border posts : border post A is obligatory connected to border B... There might be some false examples (there happens to be three-countries border posts) but in 99%, they are in the scheme A>>B and B>>A. Bouzinac 💬●✒️●💛 19:26, 5 April 2021 (UTC)[reply]

Apply to properties?[edit]

WikiProject Properties has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.

I wanted to say input device (P479) "opposite of" output device (P5196) but cannot because this prop applies to items only.

Is there a way to make it apply to props as well? If not, is there another similar prop to use?

--Vladimir Alexiev (talk) 14:44, 18 November 2021 (UTC)[reply]

@Vladimir Alexiev: inverse property (P1696) is for properties, but I don’t think P479 and P5196 are really opposite properties—the opposite would be that if some program’s item links with input device (P479) to keyboard (Q1921606), then this opposite property is used on keyboard (Q1921606) to link back to the program (but such property should not exist, bloating keyboard’s and mouse’s item with thousands of programs that use keyboard and mouse as input methods is simply useless). —Tacsipacsi (talk) 22:28, 18 November 2021 (UTC)[reply]
@Tacsipacsi: Indeed: Opposite is very different from Inverse, and I deleted some non-sensical statements --Vladimir Alexiev (talk) 06:30, 23 November 2021 (UTC)[reply]

required qualifier constraint (Q21510856)[edit]

Hello Swpb Hello Well, the majority of opposites do not have several values. You can use qualifier for this property (P8379) instead, because as a result most entries contain a warning. It is not "required", like an obligation (and the suggestion does not change this), but a "possibility". There is already allowed qualifiers constraint (Q21510851). This is not the first time that this constraint has been removed (ex: @Okkn:), so several users think like me. As you are the only one to "impose" your POV, I think it would be wise to remove this constraint as a contributor to a collaborative project. Also, single-value constraint (Q19474404) goes against your idea of multiple values separated by a qualifier and already gives a violation by separator (P4155). If you want advice, please write to me. Thank you. Cordially. —Eihel (talk) 15:52, 12 January 2022 (UTC)[reply]

The single-value constraint and the suggestion constraint aren't contradictory; they complement each other: The former says if there are multiple values, they must be differentiated by a qualifier ("In what sense are these items opposites?"). The latter says that even if there is only one value given, it's still a good idea to specify the sense in which it is an opposite, because (among other reasons) there may be other valid values not yet added. Isn't that the exact purpose of a suggestion constraint – to make the editor aware of a possible issue, without mandating that they do anything about it? I've never understood why some editors feel they need to clear any visible suggestion icons as if they were mandatory constraint violations – maybe the icon should be more subtle?
I didn't remember the constraint being removed before, but at any rate, I don't think the nature of "collaborative project" is "if it's two to one, discussion is over". From my very long experience on Wikipedia (en), that's where discussion often starts. I appreciate you starting one here; maybe I'll win over you or @Okkn:, or others, to my view, given the space and time to explain it ;). In the mean time, I've taken out the constraint for now. Relatedly, on this talk page, I've added an in-progress complex constraint that can exclude certain classes of items from the single-value constraint – feel free to add classes you think make sense. Cheers, Swpb (talk) 16:18, 12 January 2022 (UTC)[reply]
Each Item containing a unique value contains a warning with your constraint: it must have your qualifier, while it is not necessarily useful. If there is no warning, that is fine too, even if it is not a violation. separator (P4155) will also put a violation (you can also add suggestion constraint (Q62026391) to this constraint, see Q13406268 with violations). Cordially. —Eihel (talk) 16:48, 12 January 2022 (UTC)[reply]
ps: I don't know what your SPARQL query will give: timeout. —Eihel (talk) 17:13, 12 January 2022 (UTC)[reply]
"It must have your qualifier..." But that's not true: it must have the qualifier for the warning not to appear, but the warning can be ignored, as it's a suggestion; that's what I tried to explain above. Isn't that what "suggestion" means? I don't want to make the single-value with separator constraint a suggestion; that one should be mandatory. Yeah, I don't know much SPARQL; that query definitely needs work. Swpb (talk) 21:02, 12 January 2022 (UTC)[reply]
I’ve optimized the query, now it finishes well within time limit (at least for me). Probably by far the largest impact did the introduction of VALUES have: VALUES ?goodClass { wd:Q12558574 wd:Q5390013 wd:Q54989186 wd:Q49773 }. FILTER( NOT EXISTS {?item wdt:P31/wdt:P279* ?goodClass} ). lets the query executer walk the graph only once, and it filters out items as soon as any one of the listed classes is found (if I understand correctly how it works). I’ve also made some fine-tuning: dropped the support for formatter URLs (they don’t make any sense for entity-valued properties anyway) and exceptions being listed on the property page (as far as I see, all those should be excluded by the class exceptions), and rearranged the filters to put the most likely one (i.e. the one that filters out the most elements) first, so that the result set becomes as little as possible as soon as possible. (P.S. I don’t have an opinion on whether these constraints are right, I just wanted you to be able to see the data.) —Tacsipacsi (talk) 18:17, 15 January 2022 (UTC)[reply]
Incredible, thank you! Two requests: 1) can we incorporate the separators of the single-value constraint, so e.g. negative integer (Q18659417) doesn't appear? and 2) can we also ignore items that are simply subclasses of the specified classes, e.g. mainstream (Q18957)? When I try to put a * after the P31 in the query, it times out. Swpb (talk) 16:33, 18 January 2022 (UTC)[reply]
Retrieved from "https://www.wikidata.org/w/index.php?title=Property_talk:P461&oldid=2027664781"