User talk:Mahir256

For past messages, see the archive.

Bot help

Can you please help me with the lexemes? I need to change the code languages ​​from mis-x... to the appropriate code languages:

• mis-x-Q134706150 yai-latn, mis-x-Q134706143 yai-cyrl
• mis-x-Q135196768 sgh-latn, mis-x-Q135196765 sgh-cyrl, mis-x-Q135196767 sgh-arab
• mis-x-Q135183554 wbl-latn, mis-x-Q135183505 wbl-cyrl, mis-x-Q135183640 wbl-arab
• mis-x-Q135415037 yah-latn, mis-x-Q135415035 yah-cyrl
• mis-x-Q135415262 isk-latn, mis-x-Q135415260 isk-cyrl

- Rumsor (talk) 10:52, 17 January 2026 (UTC)

Help with P14108

Hi @Mahir256,

Thank you for your edit on padelleboog (L1552520), I was wondering how you got the ID from woordenlijst.org? I can't find it.

JhowieNitnek (talk) 15:49, 23 January 2026 (UTC)

@JhowieNitnek: I just added instructions to the talk page of that property. (I'm compiling a list of entries from that website that I plan to add to Mishramilan (মিশ্রমিলন) soon.) Mahir256 (talk) 15:58, 23 January 2026 (UTC)

MixnMatch issues

https://www.wikidata.org/wiki/Property_talk:P14003 https://mix-n-match.toolforge.org/#/catalog/7291

There is a rather large disparency between the items matched and the items actually being matched on Wikidata.

Same for https://www.wikidata.org/wiki/Property:P13967 and https://www.wikidata.org/wiki/Property:P13974

Any help? Trade (talk) 23:15, 27 January 2026 (UTC)

@Trade: Have you tried going to the "Manually sync catalog" entry in the "Action" menu and clicking "Update Wikidata"? Mahir256 (talk) 23:16, 27 January 2026 (UTC)

It's not my catalog and the catalog creator have been unresponsive so far Trade (talk) 23:31, 27 January 2026 (UTC)

@Trade: So? I don't have to have created the catalog to sync it; I've done this with (if I remember correctly) the Omni topic ID catalog (which Josve05a created and I merely updated). Mahir256 (talk) 23:33, 27 January 2026 (UTC)

Oh, that simple? Surprised it's not automatic Trade (talk) 23:37, 27 January 2026 (UTC)

I tried to do as you said but the batch is stuck in "INIT" Trade (talk) 23:40, 27 January 2026 (UTC)

@Trade: Then that would be QuickStatements being slow, I guess; the batches look fine otherwise, so maybe wait a bit. Mahir256 (talk) 23:41, 27 January 2026 (UTC)

Help with property proposal

Hi @Mahir256,

I recently came across the useful dictionaries of the Instituut voor de Nederlandse Taal (Q2242095) and noticed that only a few of them have dedicated properties (etymologiebank.nl ID (P12360), Wurdboek fan de Fryske taal GTB ID (P9158), Middelnederlandsch Woordenboek GTB ID (P5939), Vroegmiddelnederlands Woordenboek GTB ID (P5938), Oudnederlands Woordenboek GTB ID (P5937) and Woordenboek der Nederlandsche Taal GTB ID (P11942)).

To address this, I have been proposing properties for the other dictionaries, but I am currently stuck on Vertaal­woordenschat (Q137916170), a translation dictionary between Dutch and Arabic, Danish, Estonian, Finnish, Modern Greek, and Portuguese (in both directions). Could you help me set up the proposal(s)?

JhowieNitnek (talk) 00:51, 28 January 2026 (UTC)

@JhowieNitnek: I would not recommend adding properties for these dictionaries in the first place. (With some exceptions proposed by a now-locked user, the existing dictionary properties going between two languages were added to define words from a generally lower-resourced language into a generally higher-resourced one.) Mahir256 (talk) 20:30, 28 January 2026 (UTC)

@Mahir256 thank you for your reply but I don't think I am following? Why don't you recommend adding properties for these dictionaries in the first place?

JhowieNitnek (talk) 20:40, 28 January 2026 (UTC)

@JhowieNitnek: I am reminded of the experience of an individual who created numerous dictionary proposals going from English to another language simply because it was possible to do so; some of those proposals were rejected and some of which were created but remain largely unused. Those don't add much to English entries beyond just another number (especially when there are already other good references like the OED and Merriam-Webster that may be pointed to on English lexemes), and I fear the dictionary site you're asking about is similar in that respect (since for Dutch lexemes you already have the WNT, woordenlijst, and perhaps soon the ANW which are other good references that may be pointed to). Mahir256 (talk) 20:45, 28 January 2026 (UTC)

@Mahir256 I understand, thank you. I think you are right then. Best not to propose these properties. JhowieNitnek (talk) 20:48, 28 January 2026 (UTC)

Wiktionary as a reference

Howdy! I'm sure there is some policy/guideline that I have missed for doing such a thing on laŭ. Can you point me in the right direction, so I know what I should/should not do? TranqyPoo (talk) 23:56, 8 February 2026 (UTC)

@TranqyPoo: From Help:Sources#Different_types_of_sources: "Please note that while pages on Wikipedia (and other Wikimedia sites) can and should be added as sitelinks, they are not appropriate as sources for Wikidata statements. As per the Wikipedia policy on verifiability, the content of articles in Wikipedia must be verifiable; it should be supported by sources also (in the form of citations). However, just because something is stated on a Wikipedia page, does not mean that it is acceptable to consider the Wikipedia page itself as a source; it's much better to locate the actual citation and use that instead." Mahir256 (talk) For the purposes of lexemes, substituting "Wikipedia" with "Wiktionary" in the quoted sentences would be appropriate when considering lexemes. 23:57, 8 February 2026 (UTC)

বানান নিয়ম

আপনি দেখলাম L1556056 অপসারণ করেছেন 'বানান নিয়ম অনুসারে অপ্রয়োজনীয়' বলে। কিন্তু উইকিঅভিধানে তো ওই নাম ভুক্তি রয়েছে। তবে কি উইকিউপাত্তে এই বিষয়ে কোনো বিশেষ নীতিমালা রয়েছে? ধন্যবাদ। Redmin (talk) 16:56, 18 February 2026 (UTC)

@Redmin: এখানে দেখতে পারেন; চেষ্টা করছি যে প্রকাশিত বাংলা বানান নিয়ম অনুসারে লেমা ও শব্দরূপ লেখা হোক—এবং একাডেমি ও আকাদেমি দুটিই 'রং' লিখে। (হৃদয়ঙ্গম/হৃদয়ংগম (L308189) এরকম করে নিয়মের তুলনা দেখানো যায়।) Mahir256 (talk) 17:02, 18 February 2026 (UTC)

International Mother Language Day 2026 Wikidata Datathon

Hello Mahir256 👋🏼

Happy to invite you to participate in the International Mother Language Day 2026 Datathon, taking place from February 21 to March 3, 2026. This event is organized by WikiProject India in collaboration with Indian communities, aiming to celebrate linguistic diversity and contribute to Wikidata by enriching the content qulaity on Wikidata.

This is a great opportunity for both new and experienced contributors to engage with Wikidata and make a meaningful impact in promoting your native languages in the digital space.

If you're interested in joining, signup for the event by submitting your registration information here.

Let's come together to celebrate International Mother Language Day and strengthen multilingual representation on Wikidata. 🥳

For any questions or further details, feel free to reach out to me or post your query at the WikiProject India talk page.

Looking forward to your participation. 😊

Best regards,
User:Gnoeee 08:59, 21 February 2026 (UTC)

You are receiving this message as you are one of the active participants of WikiProject India on Wikidata. If you do not want to receive this kind of notification further, you can remove your username from here.

Lexeme:L1557131

Is the reason "not the most important lexeme in this language" exactly the right reason to delete a lexeme of the capital of the country where all native speakers live? Таёжный лес (talk) 11:51, 28 February 2026 (UTC)

@Таёжный лес: The problem is more so where this, the third lexeme ever created in this language, is merely a direct unchanged proper noun borrowing from Russian. There is already a Russian lexeme for the city, of which you are aware; that has been left alone, and simply duplicating it for all languages doesn't really help those languages much, especially (in this case) when there are likely so many other more relevant words to the average Alyutor speaker that don't have lexemes yet (and when most Alyutor speakers don't live in Moscow). Perhaps you can try creating lexemes in this language for concepts that frequently appear across languages instead. Mahir256 (talk) 12:02, 28 February 2026 (UTC)

Is this definitely matter? It's a word, which exists in the language (see wikt:Москва#Alutor, and the entry isn't empty — it contains non-trivial information about the word stem (Москва- instead of the original Москв-). Please, restore it. I can even add more linguistical information (such as declension). Таёжный лес (talk) 12:08, 28 February 2026 (UTC)

@Таёжный лес: I'll restore it if you can both add a sense with an item link pointing to the item for the city (in the same way that the Russian lexeme does) and also add the quotation and citation from the Wiktionary page you link to the lexeme as a usage example (P5831) (so that we on Wikidata know it has an existence outside of Wikimedia projects). Mahir256 (talk) 12:13, 28 February 2026 (UTC)

Okay, I'll do it. Таёжный лес (talk) 12:17, 28 February 2026 (UTC)

@Таёжный лес: Ok, please make haste with those improvements. Mahir256 (talk) 12:20, 28 February 2026 (UTC)

I have implemented your suggestions. Is there anything else I should add? Таёжный лес (talk) 12:39, 28 February 2026 (UTC)

@Таёжный лес: No I think you've done enough for now on the lexeme; thank you! Maybe add some sources to the noun class item that the lexeme is pointing to? (What off-wiki books/references define the noun classes in this language?) Mahir256 (talk) 12:44, 28 February 2026 (UTC)

Did i made it right? Таёжный лес (talk) 13:08, 28 February 2026 (UTC)

@Таёжный лес: That's enough of a start, thank you! Mahir256 (talk) 13:10, 28 February 2026 (UTC)

"télescopique" lexeme

Do we change the lemmas of lexeme that easily ?

There were a discussion on fr wiktionary that "télescopique" was used as a term for this (a nominal ellipsis, it seems it is called) I intended chariot télescopique (L1558565) to be the adjective that becomes a noun, and was probably admissible as a sense there, so I'm a bit troubled by your edits. It's not what I intended, although I had not finished and would have created this one also eventually. But it seems like reusing an item for another purpose on the Item space, so … TomT0m / talk page 15:38, 11 March 2026 (UTC)

@TomT0m: There are a couple of things at play here:

• There's a troubling tendency for speakers of languages which have a lot of resources available to them not immediately indicating those resources when creating a lexeme ('making stuff up'). As such, when I saw this new unsourced word which looked like an adjective but was marked as a noun, I started to look in Mishramilan to see if external identifier catalogs in French listed it as a noun (so that I could add an external ID as a source). Since none of those catalogs had 'télescopique' as a noun, making me think this lexeme creation to be a mistake, I then saw that instead the expanded two-word phrase did exist in Quebec's GDT. It thus made a little more sense to retain the noun sense you added but have it refer to the expanded phrase instead.
• Early on in Wikidata's lexeme development, there was a troubling tendency by a certain French-speaking editor to attach random items describing substantive concepts to lexemes that were not substantives—each of the words in "by a certain French-speaking editor" is a diff of me undoing those random attachments. The discrepancy between perceived and actual part of speech in the lexeme you created led me to believe that this was another such mistake requiring some correction.

While I did eventually find the frwiktionary discussion to which you refer, I would ask that you not tarry in the future in linking to sources you find for words. You are of course welcome to recreate the 'télescopique' noun provided that you, immediately after creating that lexeme, add the sources you found for it being used as a noun. Mahir256 (talk) 20:35, 12 March 2026 (UTC)

Well, I can understand that but, what I understand less easily it's that's asking the creator (me as it occurs) is not that hard before doing something like this ? TomT0m / talk page 21:58, 12 March 2026 (UTC)

@TomT0m: That error I will admit to, and for which I apologize. It likely did not help me as well to have as a goal recently getting the number of French lexemes that don't have meanings down to zero before this year's Wikimania, which has led me to proactively make other changes to French lexemes in the meantime. I will be sure to make a note on your talk page next time if I have further questions/comments on your edits to lexemes. Mahir256 (talk) 22:04, 12 March 2026 (UTC)

Help for Moving Pages

How do I move pages here? Darrrrmilk (talk) 00:16, 26 March 2026 (UTC)

re: Special:Diff/2475525777

This edit was so quick that I assume it was automated, but I was going to post a question about modelling anyway so I'll just ask you: Which property should I use for the relationship "pure" -> purity (Q3925914)? pertainym of (P8471) to "purity" and then item for this sense (P5137)? My understanding of "pure" is more like "with/having purity" than "of/about purity", so it's not exactly in line with the documentation you linked in that diff summary. YoshiRulz (talk) 20:41, 26 March 2026 (UTC)

@YoshiRulz: It wasn't automated, I just patrol lexeme recent changes a lot :-) You're right that using P8471 would be somewhat imprecise, but in any case that 'purity' item needs to be cleaned up a fair bit before being linked to more. For now you could use pure (Q128413576) for the physical sense of 'pure' (see the OED sense I linked on L12499-S1); for a more general sense of 'pure' applicable to non-physical/extended senses (see the OED sense I linked on L12499-S2) you can use the newly introduced pure (Q138796448). Mahir256 (talk) 20:49, 26 March 2026 (UTC)

So L12499-S1item for this sense (P5137)pure (Q128413576)? It was indeed the physical sense I was after, the opposite of chemical impurity (Q7216430). YoshiRulz (talk) 21:22, 26 March 2026 (UTC)

Request writing about Isabelle de Charriere (Q123386)

Hi Mahir256, Would you like to write about Isabelle de Charriere (Q123386) for the BN Wikipedia? It'll be appreciated if it 'll be done by somenone. Boss-well63 (talk) 00:02, 6 April 2026 (UTC)

Slow down

Hi, you made 38K edits yesterday (more than any other user on wikidata including bots), 39K the day before (top of wikidata again), and so on. Almost all bots in wikidata have been stopped since the maxlag has been quite high (phab:T421642) I assume you are using some automated editing tool (QS?) which means you need to respect Wikidata:Bots which explicitly says if maxlag is higher than 5 seconds, the script must back off until maxlag recovers. Would you mind slowing down so bots can edit again? :D Amir (talk) 12:12, 7 April 2026 (UTC)

@Ladsgroup: You are right that this tool was QuickStatements, and I unfortunately have no clue how to get browser-based QuickStatements batches to respect maxlag; perhaps this is a question for Magnus. Mahir256 (talk) 12:14, 7 April 2026 (UTC)

Yeah, I'll ask him. Thanks! In the mean time, it'd be great if you don't run a new batch until wdqs recovers (hopefully in a day or two). Amir (talk) 12:19, 7 April 2026 (UTC)

Special:Diff/2486293125

Um, I was not under the impression that this was somehow inadvisable, and I still don't really see how it is. I don't want to make tens of individual lexemes for the same noun just to express a portion of the semantic space of a single word in a single language. I tried to cover the extent of definitions for each sense (which is very broad for any Toki Pona word) and received no complaints from the Wikidata interface about it, and it seemed like the right thing to do. Where does it say that this is a bad thing? because you never specified why that is something that warrants a revert. — rae^5e <talk> 00:01, 2 May 2026 (UTC)

@Theki:

1. The thing about 'item for this sense' links is that when there are more than one on a single sense, that induces a connection between networks of equivalent senses that may not correspond cleanly. Thus a language that has distinct words for each of the concepts of 'fear', 'nervousness', and 'dread'--and which are connected to other equivalents in their distinct networks--may nevertheless find the wrong word being used in that language for one of those concepts due to a three-way connection. Even if Wikifunctions currently only considers a single "item for this sense" hop between an item and any associated senses, other systems (such as the one I work on) consider the whole network of links starting from one sense (to include any links, including other item links or "translation" or "synonym" links, more than one hop away), and such broader network considerations are susceptible to multiple links on a sense. Consider a similar situation in which a single sense had links to both woman (Q467) and something more pejorative--"the same word can be used neutrally or derisively", one might say--or links to both he (Q1196074) and she (Q1270787)--"we use the same word for 'he' and 'she' since our pronouns are gender-neutral", one might also say--and the resulting implications that can have on sense search results.
2. There is no harm in making multiple senses on a lexeme if a language in question makes such a distinction between those senses. (Indeed, some terminology dictionaries, like Catalan's TERMCAT and Quebec French's GDT, have lots of entries corresponding to specific (sub)senses of a word.) In the case of 'fear', 'nervousness', and 'dread', I wonder if there should exist a separate item whose (not necessarily direct) subclasses include all three, assuming that there is a unifying feature among them that can be specified and explicated. (WordNet gives the synset containing 'dread' as a hyponym of the synset containing 'fear', whereas the 'nervousness' synset is given as a hyponym of the 'anxiety' one; if those are reflected in subclass of (P279) statements on the items, then here I would welcome some phrasing that could serve as an umbrella over 'fear' and 'nervousness' or 'anxiety'.)
3. Having a 'single value constraint' on P5137 would be a desirable thing, but I suspect it will be better to have that constraint once the existing ~3500 senses with more than one value are disentangled--and even then just starting with the ones on common nouns. Wikidata:Lexicographical data/Documentation/Senses is where documentation on sense properties lives; while the current text doesn't outright prohibit multiple P5137s, I would interpret "something only partially related to it" to also include the situation here, and depending on how far the disentangling goes I may add more wording on that front. Mahir256 (talk) 00:27, 2 May 2026 (UTC)

I see, thank you very much for the clarification. Does this mean that items will have to be found that adequately cover a whole subset of the semantic space of certain Toki Pona words, to be used as 「item for」 values? With words like monsuta it seems obvious to me that a noun lexeme should have 「monster」 as one of its senses; I would assume that that covers the general concept of similar things such as ghouls, beasts, ghosts, other such "frightening" things.

However, with other things, like the general semantic space of 「fear」, 「nervousness」, 「dread」, etc., I'm more unsure of how to map that. My use case for this is predominantly Abstract Wikipedia. Different concepts need to be represented with a word or two in that language, and item labels make this a simple task for referring to concepts specifically, but when verbs, etc. need to be invoked it is more complicated. Of course I can't tell you how I think I should go about this since decisions are not actually finalized on a more robust method of representing our articles in a way that makes them easy to translate. My hope is that there won't have to be tens of senses on a single lexeme to cover all of its meanings and ergo allow for accurate procedural translation. At any rate, thank you again for the explanation. — rae^5e <talk> 14:37, 9 May 2026 (UTC)

Q139085943

I have a request in my talk page to restore Jerusalem, NLI, F 4699 (Q139085943) as well. @איש הישראלי work on it and other items that link to them. I don't know wיich items are about. I notified him so he probably can tell. Geagea (talk) 22:47, 14 June 2026 (UTC)

@Geagea:  Done (sorry again!) Mahir256 (talk) 22:49, 14 June 2026 (UTC)

thanks! איש הישראלי (talk) 22:53, 14 June 2026 (UTC)

Lexeme support for a gadget

Hi Mahir. Since you're both an interface admin and someone who works with lexemes, would you be interested in taking a look at my edit request to add the lexeme namespace to a list of namespaces that a gadget runs on? I think it'd be a pretty quick change, and it would make it possible to improve items like tenderness (L230052) so that the statement order matches the order of the morphemes within the lexeme. jlwoodwa (talk) 22:27, 23 June 2026 (UTC)

Marquette (L1570433)

Hello Mahir!

named after (P138) cannot be used on lexemes, check mentor (L37329) to see why. I believe the best thing to do is a chain, like you said, but with the property item for this sense (P5137). QwertyZ34 (talk) 01:28, 26 June 2026 (UTC)

@QwertyZ34: I was not suggesting using P138 on lexemes themselves, nor does P5137 lend itself to chaining; what I meant was that if any places are named after Jacques Marquette, and any other places are named after those places, then a P138 chain among those items could be established instead of dumping lots of P5137 items into a single sense; read my response to Theki above ("Special:Diff/2486293125") on the dangers of multiple P5137s on a single sense. Mahir256 (talk) 01:31, 26 June 2026 (UTC)

Just to know, is what I've done on Abbotsford (L1570429) better? Also, Marquette (Q12443) already has named after (P138); I'm searching if others also have. QwertyZ34 (talk) 01:39, 26 June 2026 (UTC)

@QwertyZ34: Yes, that is technically correct. I don't think it's the most efficient way of dealing with common place names, and I don't think it should be repeated on other lexemes (otherwise you start to assume, for example, that Northern Sámi lexemes are well-developed when that is far from the case), but I don't have the clearest idea yet of how to handle them more efficiently. Mahir256 (talk) 01:42, 26 June 2026 (UTC)

What shocked me is that New Orleans (Q34404) didn’t exist as a lexeme. Places really need expansion in lexicographical data. QwertyZ34 (talk) 01:55, 26 June 2026 (UTC)