Property talk:P2125

Documentation

• Start a query
• Properties using this qualifier (statistics)
• Count

revised Hepburn romanization
romanized Japanese following the revised Hepburn romanization system

Description	Property used as qualifier in official name (P1448), native label (P1705), name in native language (P1559), family name (P734) etc if it is presented in Japanese
Represents	Hepburn romanization (Q667558)
Data type	String
Template parameter	title or subtitle (design specific)
Domain	proper noun (Q147276) in Japanese (note: this should be moved to the property statements)
Allowed values	[A-KM-PR-WYZa-km-pr-wyzĀĒĪŌŪāēīōū !'.,:?~()0-9\-]+
Example	Tokyo (Q1490) → Tōkyō-to Gunma Prefecture (Q129499) → Gunma-ken Leiji Matsumoto (Q431443) → Matsumoto Reiji Your happiness is my happiness (Q18455755) → Anata no Shiawase ga Watashi no Shiawase
Source	https://dl.ndl.go.jp/pid/2466941/1/10
Robot and gadget jobs	DeltaBot does the following jobs: Move source to qualifier
See also	ISO 15919 transliteration (P5825)
Lists	Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P2125
Proposal discussion	Proposal discussion
Current uses	Total 42,318 Main statement 1,387 3.3% of uses Qualifier 40,918 96.7% of uses Reference 13 <0.1% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Format “[A-KM-PR-WYZa-km-pr-wyzĀĒĪŌŪāēīōū !'.,:?~()0-9\-]+”: value must be formatted using this pattern (PCRE syntax). (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/P2125#Format, SPARQL

Allowed entity types are Wikibase item (Q29934200), Wikibase form (Q54285143): 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/P2125#Entity types

Scope is as main value (Q54828448): 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/P2125#Scope, SPARQL

Scope is as qualifier (Q54828449), as main value (Q54828448): 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/P2125#Scope, SPARQL

Lexeme language: Japanese (Q5287), Ainu (Q27969): this property should only be applied to lexemes with these languages (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/P2125#language

Traditional or Revised Hepburn ?

@Mbch331, Nikki: Since there are two Hepburn methods, Traditional and Revised (Revised is used on enwiki and frwiki) which one should we use with this property ? Thibaut120094 (talk) 12:50, 7 October 2015 (UTC)

I only created this item because there was clear consensus. I don't know anything about the subject. Better ask @Nikki, Paweł Ziemian, Hsarrazin:, they seem to know more about this subject. Mbch331 (talk) 12:55, 7 October 2015 (UTC)

There aren't that many differences between the two, but I think revised (aka modified) would make the most sense, as that's the most common, e.g. Gunma Prefecture (Q129499) (traditional would be "Gumma") or Shinbashi (Q1347299) (traditional would be "Shimbashi"). By the way, the original ping didn't work, probably because you added the pings separately to signing the message. - Nikki (talk) 13:03, 7 October 2015 (UTC)

Okay, thank you for your replies. I renamed the property to remove any ambiguity. Thibaut120094 (talk) 13:20, 7 October 2015 (UTC)

I've updated the Dutch label and description accordingly. Mbch331 (talk) 13:28, 7 October 2015 (UTC)

Online tool to convert kana to Wikidata-compliant romaji?

When I search "kana to romaji" on Google this tool comes first: http://www.sljfaq.org/cgi/kana-romaji.cgi It has many options like "Hepburn" or "Simplified Hepburn". Am I right, though, that no option or combination of options produces the results we want? For instance, the two options I cited above transliterate ぐんま to gumma.

Do you know another online or offline tool that produces the transliteration we are looking for?

Thanks! Syced (talk) 02:44, 24 November 2017 (UTC)

Wikidata:Database reports/Constraint violations/P2125

Hi Nikki,

Since your changes, the bot can't update the report.

Could you take a look? Also pinging the bot owner.

Thank you. Thibaut (talk) 11:43, 18 July 2022 (UTC)

how to query for a lexeme?

@Paweł Ziemian, Hsarrazin, Nikki, Kharkiv07: this is supposed to be used on forms and not on lexemes. I would like to display the romanisation along with the the lemma. Is there a straight forward way to query it? I think I'd need to compare the lemma with all forms to figure out which romanisation represents the lemma. Maybe we can also add the romanisation to the lexeme itself? -- Loominade (talk) 11:19, 22 December 2022 (UTC)

Hello, @Loominade

I understand your problem, but have no idea how to query Lexemes... you should ask @VIGNERON : as far as I am concerned he is the expert on Lexemes and Queries ;) Hsarrazin (talk) 19:27, 11 January 2023 (UTC)

@Loominade:

To query uses of this property on Lexemes level, it's simply like that:

SELECT * WHERE {
  ?l a ontolex:LexicalEntry ;
       wdt:P2125 ?x .
}

Try it!

But there is no results (which is expected).

If you want to get the Hepburn of a form which representation is the same as the main lemma, you can do it like that:

SELECT DISTINCT ?l ?lemma ?Hepburn WHERE {
  ?l wikibase:lemma ?lemma ;
     ontolex:lexicalForm ?form .
  FILTER ( LANG(?lemma) = "ja" )
  ?form ontolex:representation ?lemma ;
        wdt:P2125 ?Hepburn .
}

Try it!

Cdlt, VIGNERON (talk) 16:43, 13 January 2023 (UTC)

@VIGNERON: thank you but I found an issue with that query. The second result is 日本/にほん (L5108) is transliterated as Nippon where it should be Nihon. The Nippon transliteration comes from the second form where the ja representation happens to be identical -- Loominade (talk) 10:29, 17 January 2023 (UTC)

@Loominade: not sure to fully understand the problem, 日本/にほん (L5108) appears twice in the results, once as Nihon for L5108-F1 and once as Nippon for L5108-F2, isn't it what you expect? Or maybe, something is wrong on L5108 ? or if you want them both on the same line, it could be done like this: https://w.wiki/6EWc ? Tell me, if it comes from the query, I may be able to correct it. Cheers, VIGNERON (talk) 19:08, 17 January 2023 (UTC)

I need a reliable way to query the transliteration for each lemma. にほん does not transliterate as Nippon. I'm not sure if 日本/にほん (L5108) should be split into but I guess it can happen that variants have matching representations with different pronunciations. I suppose we'd have to compare all representations to exactly match that of the lemma. Is this possible? -- Loominade (talk) 08:05, 18 January 2023 (UTC)