Property talk:P3108

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

Yelp ID
identifier of a place, in Yelp.com

Description	identifier of a place, in Yelp
Associated item	Yelp (Q2299611)
Applicable "stated in" value	Yelp (Q2299611)
Data type	External identifier
Domain	geographic location (Q2221906), business (Q4830453), fixed construction (Q811430), school (Q3914) or organization (Q43229)
Allowed values	[^/]+
Example	Cencio la Parolaccia (Q3664378) → cencio-la-parolaccia-roma Yelp (Q2299611) → yelp-san-francisco
Source	https://www.yelp.com/
Formatter URL	https://www.yelp.com/biz/$1
Robot and gadget jobs	Convert P553 → Q2299611 (P554 → $1) into Yelp ID → $1
Tracking: usage	Category:Pages using Wikidata property P3108 (Q39264661)
Related to country	United States of America (Q30) (See 762 others)
See also	Foursquare City Guide venue ID (P1968)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements 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/P3108 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 3,439 Main statement 3,315 96.4% of uses Qualifier 2 <0.1% of uses Reference 122 3.5% of uses
Search for values

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

Type “geographic location (Q2221906), business (Q4830453), fixed construction (Q811430), school (Q3914), organization (Q43229)”: item must contain property “instance of (P31)” with classes “geographic location (Q2221906), business (Q4830453), fixed construction (Q811430), school (Q3914), organization (Q43229)” 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). Known exceptions: John Brown Museum State Historic Site (Q14689618), Nurit Jugend (Q119712488)
List of violations of this constraint: Database reports/Constraint violations/P3108#Type Q2221906, Q4830453, Q811430, Q3914, Q43229, 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). Known exceptions: National World War I Museum and Memorial (Q6303624)
List of violations of this constraint: Database reports/Constraint violations/P3108#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).
List of violations of this constraint: Database reports/Constraint violations/P3108#Unique value, SPARQL (every item), SPARQL (by value)

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P3108#Scope, hourly updated report, SPARQL

Format “[^/]+”: value must be formatted using this pattern (PCRE syntax). (Help)

List of violations of this constraint: Database reports/Constraint violations/P3108#Format, hourly updated report, SPARQL

Qualifiers “has characteristic (P1552), subject named as (P1810), reason for deprecated rank (P2241), reason for preferred rank (P7452)”: 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/P3108#allowed qualifiers, 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/P3108#Entity types

exception for nonprofit orgs?

Manatee County Florida Democratic Party (Q99522251) has a "Community Service/Non-Profit" Yelp page that would be useful to record in Wikidata. Can an exception be made for this type? -- M2545 (talk) 08:30, 23 September 2020 (UTC)

I don't think that would make much sense unless the WikiData entry was meant to represent the geographic location or building. But instead that entry is meant to represent the political organization. The building would have to be a separate entry imo Tr3ndyBEAR (talk) 22:30, 6 December 2022 (UTC)

Yelp's internal IDs vs their URL "slugs"

Most instances of this useage use the URL slugs not the actual ID that Yelp uses internally.

For example, for Tom's restaurant the Yelp internal id is actually 6nOxwnuN0ZwLX3h3JYSJnA. And this works as a URL as well:

https://www.yelp.com/biz/6nOxwnuN0ZwLX3h3JYSJnA

Yelp takes this id and converts it to a slug to make the urls more readable so we end up with

https://www.yelp.com/biz/toms-restaurant-new-york

However, relying on this slug is much less stable imo. First of all, we don't really know how Yelp generates these or how it handles multiple restaurants with similar names or how stable they are. The internal IDs are guaranteed to always remain the same and not change.

Second of all, this slug is less useful as "data" (as in WikiData). If I'm building an app that wants to parse WikiData and map certain entries to certain properties from Yelp's dataset I need the ID not the slug! And for end-users it doesn't really matter which we use for the url since they map to the same page. The negative impacts of using slugs instead of ids are on people who want to use WikiData as an actual DATAset

Tr3ndyBEAR (talk) 22:41, 6 December 2022 (UTC)