Afrikaans العربية беларуская​беларуская (тарашкевіца) българскиBanjar বাংলা brezhoneg bosanski catalàکوردی češtinaсловѣньскъ / ⰔⰎⰑⰂⰡⰐⰠⰔⰍⰟ danskDeutsch Zazaki dolnoserbski ΕλληνικάEnglish Esperanto español eesti فارسیsuomi føroyskt français Nordfriiskgalego Alemannisch ગુજરાતી עבריתहिन्दी hrvatski hornjoserbsce magyarհայերեն Bahasa Indonesia interlinguaIlokano íslenska italiano 日本語 Jawaქართული қазақша ಕನ್ನಡ 한국어 kurdîLatina lietuvių latviešu Malagasy​Minangkabau македонски മലയാളംमराठी Bahasa Melayu Mirandés مازِرونیNedersaksies नेपाली Nederlandsnorsk bokmål norsk nynorsk occitan ଓଡ଼ିଆpolski português Runa Simi românăрусский Scots davvisámegiella​srpskohrvatski / српскохрватски සිංහලSimple English slovenčina slovenščinashqip српски / srpski svenska ślůnskiதமிழ் తెలుగు ไทย Tagalog Türkçeукраїнська اردو oʻzbekcha/ўзбекча​Tiếng Việt Yorùbá 中文
This page documents a Wikidata guideline. It is a generally accepted standard that editors should follow, though it should be treated with common sense, and occasional exceptions may apply. Changes made to it should reflect consensus. When in doubt, discuss your idea on the project chat.
This page in a nutshell:
  • A description describes and disambiguates a label using information that is free of controversy and bias
  • Keep it short—descriptions need to only be long enough to allow people to easily grasp what an item's label refers to
  • Follow style guidelines; punctuate and capitalize as if the description was appearing in the middle of a sentence
Wikidata screenshot - description field highlighted
There can be multiple items with the same label in Wikidata; descriptions disambiguate the labels
The description on a Wikidata entry is a short phrase designed to disambiguate items with the same or similar labels. A description does not need to be unique; multiple items can have the same description, however no two items can have both the same label and the same description.
Please note: this page describes the use of descriptions for items only. While properties have descriptions, their primary purpose is not to disambiguate labels; instead, they provide a brief synopsis or further details on how a property should be used (and do not necessarily follow the below stylistic conventions to do so). For more information about descriptions for properties, see Help:Properties.
Language-independent general principles
Avoid information that is likely to change
Words and phrases like "current", "incumbent", "expected", or "next year's" will eventually have to be changed. For example, if you were describing Tatsumi Kimishima, it would be better to use "fifth president of Nintendo" than to use "current president of Nintendo". While both are correct, the latter will change when Mr. Kimishima retires, while the former does not change. Just using "president of Nintendo" would also be appropriate, as it would provide enough information for successful disambiguation if, for example, there were numerous noteworthy individuals by the name of Tatsumi Kimishima.
For sportspeople, it is unwise to list the player's current team, as that also has the possibility to change. If you were describing Daniel Alves, it would be better to use "association football player from Brazil" than to use "association football player at FC Barcelona", because Daniel Alves' club may change.
Avoid opinionated, biased or promotional wording
Neutrality is a core value of Wikidata, Wikipedia and other Wikimedia projects. Try to keep descriptions neutral by avoiding opinionated or biased terms. In addition, avoid terminology that could be interpreted as promotional. "American novelist" is a neutral description while "the best novelist in America" is both opinionated and promotional.
Avoid controversial claims
Descriptions should try to reflect information both accurately and neutrally. If possible, you should avoid including controversial claims in descriptions. For example, it is better to describe the Pinnacle Islands as a "group of islands in East Asia" than a "group of Japanese islands" or a "group of Chinese islands". Remember, there will be a lot more information about an item on the page than just the description.
Follow Wikimedia namespace conventions
Wikidata contains items for several types of Wikimedia site pages that are found outside of a site's main namespace (for example, non-article pages in Wikipedia). These include templates, category pages, help pages, and Special pages. If an item is for Wikimedia site use only, it should mention the site in the description. This allows readers to know, at a glance, that they are not dealing with normal content.
Label: Top Gear
Description: Wikipedia disambiguation page
This item is the Wikipedia disambiguation page for things that are called Top Gear.
Label: Portal:History
Description: Wikipedia portal showcasing content related to the field of history
Although the inclusion of "Portal:" in the title makes it clear to people that are familiar with Wikipedia that this is a Wikipedia portal, not everyone who uses Wikidata will know what that means, so specifying that it is a Wikipedia portal still is a good idea.
Descriptions are not definitions
The concept represented by the item is defined by the statements not the description. If you need to distinguish an item from another item, add the right statements with sources before you add a special description. Also when searching items don't rely on the description's correctness, check the statements to ensure you found the right item.

Guidelines for descriptions in English
These guidelines apply to descriptions in English. Speakers of other languages may define guidelines for their language. Until that happens, the guidelines for English can be used as a starting point to the extent that they make sense and are useful for the individual language.
Descriptions are not full sentences, but small bits of information. In most cases, the proper length is between two and twelve words. One-word descriptions are almost always too ambiguous, and should be avoided. If the description goes onto a second line it is probably too long, and if it goes onto a third line, it is almost definitely too long.
Common formulas
Generally, a good starting point for a description is the class the item is an instance of (if any).
These serve as good starting points, however you should not feel bound to them.
Descriptions begin with a lowercase letter except when uppercase would normally be required or expected. Essentially, you should pretend that the description is appearing in the middle of a normal sentence, and then follow normal language rules. Most terms would not be capitalized if they appeared in the middle of a sentence. However terms such as proper nouns (e.g. the names of specific people, specific places, and specific titles) should be capitalized.
Label: Lionel Messi
Description: footballer from Argentina
This example begins with a common noun (footballer) that is not usually capitalized in the middle of a sentence, so its first letter is not capitalized here either. Argentina is a proper noun, and therefore its first letter is capitalized.
Label: Sunflower Galaxy
Description: spiral galaxy in the constellation Canes Venatici
This example begins with an adjective (spiral) that is not usually capitalized in the middle of a sentence, so its first letter is not capitalized here either.
Label: John Smith
Description: English botanist, first curator of Kew gardens (1798–1888)
This example begins with a demonym (English), an adjective that is always capitalized in the middle of a sentence, so the first letter is capitalized here too.
Descriptions are not full sentences, and should not end in periods/full stops. This is not a license to ignore punctuation entirely; if a description should have commas in it, those should be included. Wikidata takes no position whether the serial comma should be used or not used. Both "red, white, and blue" (the serial comma is after white) and "red, white and blue" (no serial comma) are acceptable in the English language. The serial comma is a contentious issue, so you should respect the initial description writer's choice to include or not include it. You do not need to reiterate the subject in the description, as it is already in the label.
Label: Miami
Description: city in southern Florida, United States
The description does use a comma, separating the state from the country, which is normal in the English language. It is not a complete sentence and does not have a period.
Label: Yoko Ono
Description: artist, author, and peace activist from Japan
This description uses a serial comma. This description could also be written without the comma after the word author, and it would be correct in the English language.
No initial articles (a, an, the)
Descriptions should not normally begin with initial articles (a, an, the). In the English language, there are some phrases that require an initial article, and in those cases you can use the initial article; however, if it is not needed, it should not be used.
Label: Dwyane Wade
Description: basketball player from the United States
Ordinary cases do not have an initial article. In this case, "a" is the proper initial article, and it is omitted.
Go from more specific to less specific
Descriptions should start with the more specific information first. When dealing with locations, for example, this might mean beginning with the municipality and ending with the country.
Label: Arcenillas
Description: municipality located in Zamora, Castile and León, Spain
In general use the local government hierarchy of names to go from more specific to less specific (Zamora is in Castile and León, which is an autonomous community in Spain). Names are separated by commas only rather than descriptions (leave out 'province of' in front of Zamora).
Label: Velika Polana
Description: town in Velika Polana municipality, Slovenia
"Municipality" included here for the first level only to distinguish the town from the municipality.
How to query them in sparql
?item schema:description ?itemdesc. FILTER​(​LANG​(​?itemdesc​) = "nl")
See also
For related Help pages, see:
For additional information and guidance, see:
English Wikipedia: Short description
Last edited on 25 August 2021, at 22:13
All structured data from the main, Property, Lexeme, and EntitySchema namespaces is available under the Creative Commons CC0 License; text in the other namespaces is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy.
Privacy policy
Terms of Use
 Home Random  Nearby  Log in  Settings  Donate  About Wikidata  Disclaimers