Wikidata:Property proposal/Lexemes

Property proposal: Generic Authority control Person Organization
Creative work Place Sports Sister projects
Transportation Natural science Lexeme

See alsoEdit

This page is for the proposal of new properties.

Before proposing a property

  1. Check if the property already exists by looking at Wikidata:List of properties (research on manual list) and Special:ListProperties.
  2. Check if the property was previously proposed or is on the pending list.
  3. Check if you can give a similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data can be transferred automatically.
  4. Select the right datatype for the property.
  5. Start writing the documentation based on the preload form below and add it in the appropriate section.
Do not use the Visual editor, because it will mess up the content of your request (the order of the template parameters will be shuffled and paragraphs are concatenated as one long string of text).

Creating the property

  1. Once consensus is reached, change status=ready on the template, to attract the attention of a property creator.
  2. Creation can be done 1 week after the proposal, by a property creator or an administrator.
  3. See property creation policy.

  On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2022/05.

Wikibase lexemeEdit

homophone lexemeEdit

   Under discussion
Descriptionlexeme with the same or very similar pronunciation as this one
Data typeForm
Example 1Laib (L493284)Leib (L613407)
Example 2eye (L3534)Ei (L6682)
Example 3交渉/こうしょう (L620305)工廠/こうしょう (L620306) (+~48 more)


I would not restrict it to words of the same language since it could help to figure out how to pronounce it. should this better be used on forms? – Shisma (talk) 16:48, 27 November 2021 (UTC)


  •   Support The Japanese language has countless homophones. For example, the word "こうしょう" is said to have 48 different homophones. This property is very useful for a language like Japanese.--Afaz (talk) 05:34, 28 November 2021 (UTC)
  •   Comment Yes, this would be better to use on forms rather on the root of the lexeme. However, this has the same problem as the translation property in that if there are many homophones, all would be listed on all of them (sort of like the old interwiki system) and thus doesn't really leverage the power of linked data. I don't have a good solution for that though. Ainali (talk) 16:26, 29 November 2021 (UTC)
    • @Ainali, Afaz: It is possible, just as with translation networks, to conceive of "homophone networks", where not all one-to-one connections need to be present for the identical pronunciation between different words to be inferable. For example, the translation network of "mother" does not have any one-to-all linkages, yet every word for mother is still linked (in)directly to every other. Similarly, of the fifty-three kanji readings of wikt:こうしょう, perhaps "交渉" could just link to other lexemes containing "交" or "渉", rather than to all of the fifty-two others listed on that page. Mahir256 (talk) 05:28, 1 December 2021 (UTC)
    here's an example where forms are homophone but not the lemma: rasieren (L450732) (F4: verb, present tense: rasiert) rasiert (L622301) (F1: adjective, positive: rasiert) – Loominade (talk) 08:18, 8 December 2021 (UTC)
  •   Support Could it be used on lexemes with the understanding that it means at least one of the forms of the subject lexeme has the same pronunciation as one of the forms on the value lexeme? ArthurPSmith (talk) 18:37, 29 November 2021 (UTC)
  •   Comment: What do we do about words that are homophonous in some regional pronunciations but not others, e.g. the cot–caught merger (Q28401088)? Are there existing properties that could be used as qualifiers? ⁓ Pelagicmessages ) 14:59, 8 December 2021 (UTC)
    pronunciation variety (P5237) could be used as a qualifier perhaps? ArthurPSmith (talk) 18:16, 8 December 2021 (UTC)

@Shisma, Afaz, Ainali, ArthurPSmith, Mahir256: Please consider supporting Wikidata:Property proposal/homophone form rather than this one. Or consider if it makes sense to have both properties. --Loominade (talk) 10:34, 10 December 2021 (UTC)

  • You're right. It's allways the form only. Singular Laib and Leib are homophone. Plural Laibe and Leiber are not. --Vollbracht (talk) 21:32, 4 February 2022 (UTC)
  •   Support, an important property for the language.--Arbnos (talk) 23:51, 23 April 2022 (UTC)

homophone formEdit

   Ready Create
Descriptionform with the same or very similar pronunciation as this one
Data typeForm
Example 1rasieren (L450732)-F4 (singular, active voice, present tense, third person, indicative) ⟷ rasiert (L622301)-F1 (predicative, positive)
Example 2haben (L4179)-F3 (singular, active voice, present tense, second person, indicative) ⟷ hassen (L622636)-F4 (singular, active voice, present tense, second person, indicative)
Example 3Laib (L493284)-F1 (singular, nominative case) ⟷ Leib (L613407)-F1 (singular, nominative case)


Hast du Tee?
Ja, ich hasse Tee!

Loominade (talk) 10:03, 10 December 2021 (UTC)


  •   Support --- Jura 12:38, 10 December 2021 (UTC)
  •   Comment I don't think the first example is useful, that is linking two different parts of speech that would be used in different context and wouldn't be confused (and they are already etymologically linked anyway aren't they?) Should this be restricted to only cases where the two forms are in the same language and have the same lexical category and grammatical features? ArthurPSmith (talk) 18:44, 10 December 2021 (UTC)
    know! --- Jura 17:48, 13 December 2021 (UTC)

Phrase in Hiero MarkupEdit

   Under discussion
Descriptionhieroglyphs written in Wikihiero syntax
Representshieroglyph (Q193762)
Data typeString
DomainJede Phrase, die aus Hieroglyphen besteht. Bsp.: Sakkara-Präfix 1 (Q110630171)
Allowed valuesWikiHiero syntax. Don't include <hiero></hiero> tags
Example 1Djedefre (Q209397) → Namensprefix:
Example 2Khufu (Q161904) → Namensprefix:
Example 3Saqqara king (Q110550976) → Namenspostfix:
SourceKönigsliste von Sakkara (Q1054563)
Planned useEntwicklung von Vorlagen, die Elemente von Königslisten darstellen
Wikidata projectWikiProject Ancient Egypt (Q10640407)


Einigen strukturierten Daten können regelmäßig auftretende Phrasen zugeordnet werden. Das können Präfixe für Namen, wie das typische Nisut-Biti vor Thronnamen, oder ein "Möge er ewig leben" hinter dem Königsnamen auf dem Ebers-Kalender, oder eine spezifische Datumsangabe sein. Wann immer eine Phrase nicht der Beschreibung eines Namens, oder sogar nicht einmal einer Person dient, verbietet sich die Verwendung von Name in Hieroglyphen-Syntax (P7383) . Dabei sollte dieses Property als Variante des hier vorgeschlagenen begriffen werden. Vollbracht (talk) 03:25, 21 January 2022 (UTC)


@Vollbracht: is this property designed for lexeme or item? All exemples you gave are items. Pamputt (talk) 10:53, 21 January 2022 (UTC)
So it is for items at least. But for shure we'll find a usage in a lexeme in future. Vollbracht (talk) 16:57, 21 January 2022 (UTC)
What about Hudjefa (Q1300872) or Sedjes (Q1633800)? These are no names. "Hudjefa" means destroyed or wiped out, saying the name of the Pharaoh labeled this way was illegible by the time of 19th Egyptian dynasty already and "sedjes" means "omitted" or "missing". These in actual fact should be lexemes, shouldn't they? Vollbracht (talk) 20:06, 22 January 2022 (UTC)
Correction: Each name prefix has a meaning, is a title, or what ever. This title is a lexeme, isn't it? So what other Form to put it would you suggest? Vollbracht (talk) 22:07, 4 February 2022 (UTC)

HSK levelEdit

   Under discussion
DescriptionChinese lexeme vocabulary level in HSK (Hanyu Shuiping Kaoshi)
RepresentsHanyu Shuiping Kaoshi (Q535477)
Data typeQuantity
Allowed values[1-6]{1}
Example 1喜欢/喜歡 (L3511) → 1
Example 2筷子 (L6602) → 3
Example 3东西/東西 (L312663) → 1


The grade number can be get at or searched on a third-party website of CEDICT (Q2931247) ( The help page is on .

Kethyga (talk) 08:19, 31 January 2022 (UTC)


  •   Comment I changed the datatype to Quantity (also fixed the English label - it's not an ID!) - however maybe it should be item-valued with new items created corresponding to the 6 language levels? ArthurPSmith (talk) 18:10, 31 January 2022 (UTC)
  •   Comment would support if the change Arthur suggests is made. Mahir256 (talk) 22:34, 1 February 2022 (UTC)
    +1–So9q (talk) 13:27, 18 February 2022 (UTC)
  •   Neutral This is basically another version of Wikidata:Property proposal/member of lexicon.--GZWDer (talk) 17:51, 11 May 2022 (UTC)
    My initial plan is like grade of kanji (P5277) which devide the vocabulary to different order. Kethyga (talk) 22:14, 11 May 2022 (UTC)

Kubbealti Lugati term IDEdit

   Under discussion
DescriptionIdentifier for the online version of Q6053582
Data typeExternal identifier
Example 1berilyum (L6318)berilyum
Example 2karpuz (L11577)karpuz
Example 3eylül (L8744)eylül
Number of IDs in source~46k (reference)
Formatter URL$1


A Turkish dictionary. It also includes words that have been translated from Arabic and Persian into Turkish. It will be useful for Turkish-knowing users. Devrim ilhan (talk) 02:06, 8 May 2022 (UTC)

Edit: I am sorry. I noticed that the links are not working in the screenshots I took with It works when I enter from Turkey. I hope it's temporary.--Devrim ilhan (talk) 03:17, 8 May 2022 (UTC)


  •   Oppose only because, if this property is meant to be used on lexemes, the examples should involve lexemes—and not items as is currently the case. Mahir256 (talk) 02:51, 8 May 2022 (UTC)
@Mahir256:, The examples have been fixed. I thought it could be used on other pages as well, but it seems better if it's only used on Lexeme pages. Are the links working for you now? --Devrim ilhan (talk) 04:57, 8 May 2022 (UTC)



Wikibase formEdit

Wikibase senseEdit