Property talk:P4011

Documentation

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

Semantic Scholar paper ID
identifier for an article in the Semantic Scholar database (40 hexadecimal digits; for numeric ID see P8299)

Description	identifier for an article in the Semantic Scholar database
Represents	Semantic Scholar (Q22908627)
Associated item	Semantic Scholar (Q22908627)
Applicable "stated in" value	Semantic Scholar (Q22908627)
Data type	External identifier
Domain	work (Q386724) (note: this should be moved to the property statements)
Allowed values	[0-9a-fA-F]{40}
Example	The Semantic Web Revisited (Q29037447) → 5acd1dd3da5752e1de4c5b46f75b7aec2bc50503 Occupational Safety and Health in Peru (Q40166441) → 4eb67f8548f76574864003baf314e8141f354cba
Source	https://www.semanticscholar.org/
Formatter URL	https://www.semanticscholar.org/paper/$1
Tracking: usage	Category:Pages using Wikidata property P4011 (Q55924937)
See also	Semantic Scholar corpus ID (P8299), Semantic Scholar author ID (P4012), Semantic Scholar topic ID (P6611), Google Scholar paper ID (P4028), CiteSeerX article ID (former scheme) (P3784), PubPeer article ID (P7381), ORKG ID (P10897)
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/P4011 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 18,414 Main statement 18,348 out of 224,132,803 (0% complete) 99.6% of uses Qualifier 2 <0.1% of uses Reference 64 0.3% of uses
Search for values

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

Format “[0-9a-fA-F]{40}”: value must be formatted using this pattern (PCRE syntax). (Help)

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

Item “instance of (P31)”: Items with this property should also have “instance of (P31)”. (Help)

List of violations of this constraint: Database reports/Constraint violations/P4011#Item P31, hourly updated report, search, 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/P4011#Unique value, SPARQL (every item), SPARQL (by value)

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).
List of violations of this constraint: Database reports/Constraint violations/P4011#Single value, 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/P4011#Entity types

Item “Semantic Scholar corpus ID (P8299)”: Items with this property should also have “Semantic Scholar corpus ID (P8299)”. (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/P4011#Item P8299, search, SPARQL

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/P4011#Scope, SPARQL

Conflicts with “instance of (P31): human (Q5)”: this property must not be used with the listed properties and values. (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/P4011#Conflicts with P31, search, SPARQL

Why should I add this property?

I have just created a number of scholarly article (Q13442814) items that might benefit from my adding their Semantic Scholar paper ID (P4011). I'm not sure of the value of adding this property to these items. I'm happy to do the work, but I'd like a little feedback on why it's worthwhile or if my time is better spent adding/editing other items. Any takers? Thanks. Trilotat (talk) 18:24, 28 August 2019 (UTC)

Trilotat, it's mainly a benefit if Semantic Scholar has the full text, because then it produces an analysis of the references, extracts figures etc. There is no need to add this identifier manually: Unpaywall has 3 million IDs in its latest dump, we can import these. It might be worth curating the IDs after they're imported, though. Nemo 22:41, 29 November 2019 (UTC)

Pintoch, do you think you can import these with your bot? Nemo 22:43, 29 November 2019 (UTC)

I am unlikely to find the time to work on that any time soon, sorry! − Pintoch (talk) 10:52, 30 November 2019 (UTC)

I'm told the IDs in the latest dump are sometimes outdated (since deleted), so it's probably better to wait for the next dump. Nemo 16:14, 3 December 2019 (UTC)

Constraint Corpus ID

The Semantic Scholar API [1] always returns the hex paperID (P4011) but not the Corpus ID. OTOH {{P|4011}} requires a {{P|8299}} stmt because of a constraint made. So I propose to remove that constraint as long as there is no way to get the {{P|8299}} programmatically from S2. This would also remove 13786 existing violations. --- SCIdude (talk) 08:27, 29 September 2022 (UTC)

PS: I was wrong, the Corpus ID can be requested through the ExternalIds field in the S2 paper API. Still, I see no reason for the constraint and propose to remove it. --SCIdude (talk) 08:55, 29 September 2022 (UTC)