Property talk:P646

Format “/m/0(?:[0-9b-df-hj-np-tv-z_]{2,7}|1[0123][0-9b-df-hj-np-tv-z_]{5,6})”: value must be formatted using this pattern (PCRE syntax). (Help)

"exceptions" is incompatible with "mandatory" parameter List of violations of this constraint: Database reports/Constraint violations/P646#Format, hourly updated report, SPARQL

Conflicts with “instance of (P31): Wikimedia template (Q11266439), Wikimedia category (Q4167836), Wikimedia module (Q15184295)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P646#Conflicts with P31, hourly updated report, 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).
List of violations of this constraint: Database reports/Constraint violations/P646#Single value, SPARQL

Distinct values: this property likely contains a value that is different from all other items. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Notamacropus parma (Q109262322), Macropus parma (Q209731), Macropus irma (Q209648), Notamacropus irma (Q112307733), appetizer (Q1628963), entrée (Q6545590), first course (Q11942732), feather (Q81025), icemaker (Q4271166)
List of violations of this constraint: Database reports/Constraint violations/P646#Unique value, SPARQL (every item), SPARQL (by value)

Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410)”: 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/P646#Conflicts with P31, search, SPARQL

Qualifiers “determination method or standard (P459), reason for deprecated rank (P2241), reason for preferred rank (P7452), subject named as (P1810), quotation (P1683), mapping relation type (P4390), applies to part (P518)”: this property should be used only with the listed qualifiers. (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/P646#allowed qualifiers, 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/P646#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/P646#Entity types

Type “entity (Q35120)”: item must contain property “instance of (P31), subclass of (P279)” with classes “entity (Q35120)” 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/P646#Type Q35120, SPARQL

Pattern ^(/g/[0-9a-zA-Z_]{8,10})$ will be automatically replaced to \1 and moved to Google Knowledge Graph ID (P2671) property. Testing: TODO list

Pattern ^(m/0[0-9a-z_]{2,7})$ will be automatically replaced to /\1. Testing: TODO list

Pattern ^(g/[0-9a-zA-Z_]{8,10})$ will be automatically replaced to /\1 and moved to Google Knowledge Graph ID (P2671) property. Testing: TODO list

This entity (P646) is used by Wikimedia's setting of Wikidata. Please contact the development team or file a bug on Phabricator before big changes (renaming, deletion, merging, etc.).

This property is being used by: ar:قالب:معرف فريبيس eu:Txantiloi:Eskoziako udalerri infotaula automatikoa, eu:Txantiloi:Irlandako Errepublikako udalerri infotaula automatikoa, eu:Txantiloi:Dublingo barruti infotaula automatikoa, eu:Txantiloi:Belfasteko auzo infotaula automatikoa, eu:Txantiloi:Corkeko auzo infotaula automatikoa, eu:Txantiloi:Derryko auzo infotaula automatikoa, eu:Txantiloi:Galwayko auzo infotaula automatikoa, eu:Txantiloi:Limerickeko auzo infotaula automatikoa d:Template:Tr peoplelist 4, d:Template:Tr peoplelist 8 de:Vorlage:Filmdaten, de:Vorlage:Filmdaten/1 hu:Sablon:Focis linkek cy:Nodyn:Cyffuriau hy:Կաղապար:Տեղեկաքարտ Ձիու ցեղատեսակ zh-yue:Template:電影拎, zh-yue:Template:人物拎 my:တမ်းပလိတ်:Art links hak:模板:Ngoi-phu lièn-kiet yue:Template:人物拎, yue:Template:電影拎 Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Wouldn't it be simpler to just have it as 0123abc instead of /m/0123abc? — PinkAmpers&^{(Je vous invite à me parler)} 23:35, 19 June 2013 (UTC)[reply]

Und was ist der Nutzen dieses Zeugs? --Enzian44 (talk) 18:40, 10 September 2013 (UTC)[reply]

Damit wird ausgesagt, dass die beiden IDs die gleiche Sache bezeichnen. Bots und Tools können dann den Link weiterverfolgen, und die Daten verknüpfen oder abgleichen. Das ist vergleichbar zu solchen Properties wie Property:P839, Property:P498, Property:P345, etc. --Denny (talk) 18:08, 14 November 2013 (UTC)[reply]

Freebase has 2 kinds of identifiers, mid and the old guid. Will this be just for holding mids only ? Thadguidry (talk) 02:20, 7 January 2015 (UTC)[reply]

According to the format filter above, this only workd with mids. But since everything that has a guid also has a mid, this shouldn't be a problem. --Denny (talk) 16:09, 8 January 2015 (UTC)[reply]

This could a a problem in the future, if Freebase reorganises the structure of its website. Obviously the "/m/" part should be part of the base URL (along with the protocol and domain name). Note that the base URL is not even a canonical URL (with the trailing slash, i.e. the leading "/" in "/m/" is in fact part of the URL and not part of the id; the "m/" is also subject to changes, if ever Freebase wants to index other things with new types of identifiers, or wants to extend the IDs with new formats, in which case there will be synonyms for the older id's, using either the old format under "/m/" or a newer format somewhere else).

Freebase could as well provide new querying interfaces using quarty strings in which this "/m/" prefix will have no meaning.

We should use only Ids that are limited to the most restrictive unique part and not use common parts that are in fact in the base URL.

There's absolutely no good value for keeping this "/m/" prefix. Verdy p (talk) 20:53, 31 March 2016 (UTC)[reply]

See also the discussion below: the "/m/" prefix is now "m." with the new interface !

Let's drop that "/m/" now (a bot could do the work, but we should update the regexp to make it first optional, another bot will drop this bad prefix everywhere). Verdy p (talk) 20:56, 31 March 2016 (UTC)[reply]

How can I get MID, and GUID? Arjundahalard (talk) 11:30, 16 June 2021 (UTC)[reply]

There have been some discussions about Google pushing this property. Now there is a new bot request:

• Wikidata:Requests for permissions/Bot/DennyBot

--Kolja21 (talk) 09:39, 1 December 2013 (UTC)[reply]

 Done Withdrawn by Google employee after creating Freebase Data Dumps (Q15241312). Now Legobot is adding the Freebase id. --Kolja21 (talk) 12:23, 7 December 2013 (UTC)[reply]

If instance of (P31) is a Wikimedia disambiguation page (Q4167410) the presence of Freebase ID (P646) is prohibited

see: Wikimedia disambiguation page (Q4167410) with Freebase identifier (P646) . Usualy there might be two possibilities:

a) please identify the non - ambiguation page (WD item) where the property Freebase identifier should be moved;
"normally" no other statements should be left at the disambiguation page;
it can happen that a set of properties should be moved to another (a second) WD item, another set to a third WD item etc.

b) verify which language is a disambiguation page and separate it from the rest; please use Gadget-labelLister.js ^{can be activated at preferences#gadgets} to remove all faulty descriptions after the disambiguation page is separated (the languages are de, en, fr, es, pt, pt-br, ru, sv and possibly some others).

Thanks in advance! gangLeri לערי ריינהארט (talk) 19:51, 26 May 2014 (UTC)[reply]

Ping! Zeitoun (Q4116309) still found today. There are 1114 items. Who is responsible for this? Regards gangLeri לערי ריינהארט (talk) 19:36, 16 June 2014 (UTC)[reply]

This can happen at any time on any Wikimedia: frequently pages are renamed because new homonyms are found, and the former name becomes a desambiguation page.

The constraint violation will help locate them and will help fixing possible cases of homonyms in other wikis which still don't have a desambiguation page, but that should have one because of other articles pointing to the non-qualified article speaking in fact about another topic.

We will never stop the ongoing flow of violations of this constraint because pages renamed in Wikipedia are automatically feeding their own entries in Wikidata.

Well, this flow is usually decelerating, because most cases of homonyms are already resolved for the most frequently referenced topics in major wikipedias. But some Wikipedias are also growing very fast when they are fed by bots (e.g. Malagasy Wikipedia) and after the bot has filled in many pages automatically (using some automated translation), there are many pages renamed to set the actual name, and many cases of homonyms are occuring in that language, possibly conflicting with many other topics which are not homonyms in other languages.

So asking about "who" is doing that, is not relevant as this comes from various people (that don't even work in Wikidata but work locally in their Wikipedia).

The solution for this problem would be to improve the bots installed in Wikipedia that feed Wikidata with new homonyms, when pages are renamed. But as this requires action in Wikidata in all cases, all we can do is to have a tracking feed for those renamings occuring in each Wikipedia (or Wikisource, Wikinews...) and that create violations here.

In fact, the existing violation report here on Wikidata already plays this tracking role. But this requires more people to resolve them, or some new bots trying to resolve these violations here, by creating the missing elements and "recategorizing" the existing data linked to wikis where no disambiguation page still exist as they currently don't have cases of homonyms.

Another solution would be to develop a bot feeding a report on those wikidatas which still don't have disambiguation pages for some topics (but this requires a local team to work on this project: note that there are frequent cases where a Wikipedia edition is speking about several topics on the same page, in distinct sections, when others have splitted the topic in distinct articles. The main article acts then as is it was a disambiguation page, but presents them in the generic article in more details than with a simple disambiguation page (there may also be links to detailed articles for subtopics).

Also Freebase may not distinguish all these related subtopics, and can still group them under the same subject, even if Wikipedia is desambiguating it to multiple distinct subtopics (that don't have any Freebase identifier for them alone): this case occurs notably for topics that are "classes" (whose "instances" are the subtopics).

I don't see any easy solution for that. We must live with recurrent violations of this constraint, which are not strictly violations, but only trackers of possible problems of ambiguity. Verdy p (talk) 16:22, 31 March 2016 (UTC)[reply]

Since Freebase has become write-only on March 31 and will be shut down in June, I think that this property should be cancelled.--Fringio (talk) 18:05, 1 April 2015 (UTC)[reply]

I don't agree. I think it is very importatnt by the data/reference transfer which should start very soon (@Denny:). Matěj Suchánek (talk) 18:15, 1 April 2015 (UTC)[reply]

(Disclosure: I work for Google, who run Freebase) I agree with Matěj. Also, Google plans to offer a new API, which will also allow to access the data using the Freebase Mid, which means in Wikidata we will only need to change the URL-pattern. One way or the other, let us at least wait until the Mids are actually indeed not useful anymore. --Denny (talk) 18:32, 1 April 2015 (UTC)[reply]

We have now formatter URI for RDF resource (P1921) which I'd like to add here but Freebase has this unfortunate peculiarity that the m-id, like /m/09c7w0, are not part of the URI of the RDF identity, instead, / is replaced with ., so the ID becomes m.09c7w0. See: https://developers.google.com/freebase/v1/rdf-overview#mapping

It may be not very important since Freebase is being phased out anyway, but it'd be nice to have some solution if possible. --Laboramus (talk) 19:28, 4 June 2015 (UTC)[reply]

How can I get URI? And what are the values p(....) mentions, having numbers between brackers, and P alphabet at beginning. I found Wikidata has similiar with Q alphabet. Arjundahalard (talk) 11:24, 16 June 2021 (UTC)[reply]

Currently we have mids like:

• Q3341764 > https://www.freebase.com/m/08c_0g that gives: mid: /m/08c_0g replaced by: /m/03q2jtt
• Q1193055 > https://www.freebase.com/m/047sd2p that gives: mid: /m/047sd2p replaced by: /m/04wjkbv

These should probably be updated. --- Jura 07:22, 19 July 2015 (UTC)[reply]

The link to Freebase.com currently doesn't work. --Harry Canyon (talk) 08:42, 25 February 2016 (UTC)[reply]

You need to contact the development team about it.
--- Jura 08:53, 25 February 2016 (UTC)[reply]

Phab:T128078.
--- Jura 12:44, 27 February 2016 (UTC)[reply]

@Harry Canyon, Jura1: Freebase has gone offline, see Wikidata:Properties for deletion. --Kolja21 (talk) 16:37, 20 May 2016 (UTC)[reply]

I think the link pattern could be replaced by https://g.co/kg$1 unless there is a better link pattern. --Denny (talk) 19:53, 20 May 2016 (UTC)[reply]

Oh, I see, that's already in the statements. --Denny (talk) 19:54, 20 May 2016 (UTC)[reply]

Hi. Can you tell me why some items continue to use the old link pattern and others the new one, and if there is any action to take? Pietro (talk) 19:51, 30 May 2016 (UTC)[reply]

The Freebase IDs now link web.archive.org: how to manage the current links? There is any way to migrate to Google Knowledge Graph identifier (P2671)? Pietro (talk) 11:39, 7 August 2016 (UTC) Adaption would be nice :) . Thank you, Conny (talk) 09:23, 23 November 2016 (UTC).[reply]

Should the property be renamed to Knowledge Graph ID and linked to Knowledge Graph? Possibly time based? This is the current purpose of the ID.--CENNOXX (talk) 10:46, 12 June 2018 (UTC)[reply]

There is Google Knowledge Graph ID (P2671). Matěj Suchánek (talk) 14:53, 12 June 2018 (UTC)[reply]

Can't seem to find a place to search for existing entries. Bogger (talk) 11:17, 4 July 2018 (UTC)[reply]

Bogger me too. I tried months ago to find a way to get this code but I failed. Before I try again, does anyone has any advice? I am adding geonames ID to some local items but I can find onyl a limited percentage of them, these ID will be very useful.--Alexmar983 (talk) 13:50, 28 July 2018 (UTC)[reply]

So far I mostly see bots adding them in the page history. maybe I could write to the main village pump or at least another technical village pump, I really would like to learn and teach how to insert this ID.--Alexmar983 (talk) 13:54, 28 July 2018 (UTC)[reply]

Bump! Bogger (talk) 08:05, 14 May 2020 (UTC)[reply]

Bump! Bogger (talk) 11:16, 14 January 2021 (UTC)[reply]

@Bogger: you can search in https://angryloki.github.io/mreid-resolver/ by name, or sometimes even by Wikidata ID. --Lockal (talk) 07:35, 22 January 2021 (UTC)[reply]

Both the Google Knowledge Graph ID (Property:P2671) and Freebase ID (Property:P646) links aren't working. Is someone able to see and understand why? --Omert33 (talk) 07:46, 15 January 2019 (UTC)[reply]

See this discussion for explanations. Tpt (talk) 10:16, 20 January 2019 (UTC)[reply]

Good morning, I am writing and greeting you from Calabria. Now well, my request is very simple. Ms. Cadeo has been single for quite a while, they are now 4 years old here the proof and also [1], but still today Wikidata and wikipedia and consequently Google is slow to update. what do you advise me to do? Help me ..., sure of your answer and solution, I thank you in advance and I hope to return the courtesy. With regard--Luigi Salvatore Vadacchino (talk) 16:38, 15 March 2020 (UTC)[reply]

@Luigi Salvatore Vadacchino: The statement is correctly qualified with end time (P582) in Wikidata and I've now added the freebase ID to the item. Wikidata doesn't have any direct authority over Google's search results, the depicted subject or an official representative of the depicted subject could claim the knowledge panel via [2] (this link is how I found the freebase ID) if they wanted to make sure it was always up to date. Any third party can also provide feedback to tell Google which part of the knowledge panel is wrong. Both of these options I just found as buttons underneath the knowledge panel which appears when searching. Hope this helps. --SilentSpike (talk) 08:59, 15 May 2020 (UTC)[reply]

I've changed preferred URL formatter from https://freebase.toolforge.org to https://google.com, because I've discovered, that there are identifiers, which exist in Google version and missing in toolforge dump (e. g. compare https://freebase.toolforge.org/m/010qx6n8 and https://www.google.com/search?kponly&kgmid=/m/010qx6n8&hl=en) . freebase.toolforge.org has also issues with link creation to google.com (it sometimes breaks if browser locale is other than English). Current formatter is carefully crafted (see Property talk:P2671#Links working again) and hopefully should work for all ids. --Lockal (talk) 11:34, 24 November 2020 (UTC)[reply]

Lockal, but why &hl=en is added, instead of allowing default user interface language? 2001:7D0:81F7:B580:7092:BCC9:1F14:C76B 08:09, 13 January 2021 (UTC)[reply]

Oh, I see, otherwise "it sometimes breaks". Is this common, are there examples? If it generally works for other languages too, then maybe it'd be still better to prefer default language. 2001:7D0:81F7:B580:7092:BCC9:1F14:C76B 08:19, 13 January 2021 (UTC)[reply]

Yes, Google has issues with non-english languages (especially for non-common languages). Each item in Freebase and Google Knowledge Base has a set of labels in various languages. In some cases these labels are imported from Wikipedia, Wikidata of from somewhere else, in some cases these labels are autogenerated (e. g. Russian names are autotransliterated). When there is no label, viewing entry in google.com fails with various issues.

• Worst case example: when item is ambiguous and highly unbalanced, and there is no high-confidence label in non-english default user interface language, Google displays wrong knowledge box. For example, there are famous British Prime Minister David Cameron and less known Canadian judge David Cameron (/g/12148r5j).
  • https://www.google.com/search?kgmid=/g/12148r5j&hl=en - viewing in English works fine
  • https://www.google.com/search?kgmid=/g/12148r5j&hl=zh - viewing in Chinese shows wrong knowledge card (of Prime Minister), which is a disaster, IMO
  • https://www.google.com/search?kgmid=/g/12148r5j&hl=ru - viewing in Russian works fine now, but it did not work until I did this edit, which increased confidence level of Russian label.
• More common case: few labels: Bek-Bulat - /g/1pznmqc2p
  • https://www.google.com/search?kgmid=/g/1pznmqc2p&hl=ru - works best in Russian
  • https://www.google.com/search?kgmid=/g/1pznmqc2p&hl=en - works mediocre in English (but still works)
  • https://www.google.com/search?kgmid=/g/1pznmqc2p&hl=zh - does not output knowledge box for Chinese users; Chinese Wikidata users may think that identifier is wrong, but it isn't
• When item has only labels in Chinese and Japanese (not related to Wikidata, just an example): /g/11h7dqtc4b:
  • https://www.google.com/search?kgmid=/g/11h7dqtc4b&hl=ja - viewing in Japanese works fine
  • https://www.google.com/search?kgmid=/g/11h7dqtc4b&hl=en - viewing in English does not work

--Lockal (talk) 09:07, 13 January 2021 (UTC)[reply]

I lean towards not hardcoding English if it also doesn't always give the best result, or it may not work at all, and as localized data hopefully gets more sufficient/complete over time. 2001:7D0:81F7:B580:98BE:B08E:26FC:6041 11:20, 13 January 2021 (UTC)[reply]

I'm just afraid that non-english Wikidata users would then silently remove such ids (without understanding, that browser locale is to blame). I've also tried to contact Google (using Feedback button), but as I expected, without any result. I've also just asked this question - https://support.google.com/websearch/thread/93293750?hl=en - I suggest to wait for answers. --Lockal (talk) 13:42, 13 January 2021 (UTC)[reply]

On Google Dev page, Freebase service is no longer available. What the external link for Freebase ID (P646) be deprecated on a global scale? Thank you. ShiehJ (talk) 19:35, 5 March 2021 (UTC)[reply]

Is it still possible to get a Freebase ID? Arjundahalard (talk) 11:06, 16 June 2021 (UTC)[reply]

I found Google Knowledge Graph with beginning from alphabet P, and Wikidata id beginning from alphabet Q. How can I get a PID? Or is PID (Persistent Identifier), as generally talked? Arjundahalard (talk) 11:14, 16 June 2021 (UTC)[reply]

I just removed the property of Grey (Q14756698) because the associated concept is empty and therefore redirects to the Google home page (the value was /m/0_tgz4z).

It is possible that there are other values with the same problem but being more than seven million it is difficult to check all of them without Google blocking my access due to "unusual traffic". So I would like someone else to check this.

The same thing could also be happening with Google Knowledge Graph ID (P2671).--Swicher (talk) 05:43, 18 February 2022 (UTC)[reply]

Some ID's like /m/0101c5cf (Film and Art Festival Two Riversides (Q116556396)) and /m/011bzyd7 (Olga Tuktareva (Q117037607)) are not matching the current regex but work OK on Google. So basically that regex needs to be adjusted especially because when I enter the correct ID in both cases the last character is automatically removed before I can save/publish it. - Robotje (talk) 12:23, 26 March 2023 (UTC)[reply]

This item has both Freebase ID (P646) and Google Knowledge Graph ID (P2671). Could you please suggest me how to fix it?-- Carnby (talk) 10:44, 24 September 2023 (UTC)[reply]

In this article, I don't know why Freebase ID have a problem. I think I found right Id, but still problem. Please let me know what's the problem in this article Q131188847! Hee Jung, Yoon (talk) 06:51, 15 November 2024 (UTC)[reply]