Hello New Freebase :)
I have updated the OpenRefine reconciliation redo task to support reconciling against Wikidata here: https://github.com/OpenRefine/OpenRefine/issues/805
However, in our inspection of your API, would could not find a close approximate for something that the Freebase API had, which was OUTPUT of Properties for each Entity / Item that is returned with a search, as shown in examples here:
ALL http://freebase-search.freebaseapps.com/?filter=(all+type%3A%2Feducation%2Fe...
and
PART OF http://freebase-search.freebaseapps.com/?filter=(all+type%3A%2Feducation%2Fe...
Looking at the Wikidata API, this query syntax does not provide additional property (CLAIM) details:
https://www.wikidata.org/w/api.php?action=wbsearchentities&search=Valve&...
I would ideally like to have a way to output STATEMENTS or CLAIMS and their values. An ALL CLAIMS parameter, as well as providing which CLAIMS perhaps separated by | pipe.
Is there a way to do so now with the current implementation somehow ?
Thanks in advance, Thad +ThadGuidry https://www.google.com/+ThadGuidry
It seems that the nearest equivalent with Mediawiki would be with this syntax:
https://www.wikidata.org/w/api.php?action=wbgetentities&sites=enwiki&...
however...what is really needed is a &search= with perhaps a default limit of 5 entities returned, like so:
https://www.wikidata.org/w/api.php?action=wbgetentities&sites=enwiki&...
Unfortunately, the &search= is not available with action=wbgetentites BUMMER.
Thad +ThadGuidry https://www.google.com/+ThadGuidry
On Tue, Jan 6, 2015 at 11:04 AM, Thad Guidry thadguidry@gmail.com wrote:
Hello New Freebase :)
I have updated the OpenRefine reconciliation redo task to support reconciling against Wikidata here: https://github.com/OpenRefine/OpenRefine/issues/805
However, in our inspection of your API, would could not find a close approximate for something that the Freebase API had, which was OUTPUT of Properties for each Entity / Item that is returned with a search, as shown in examples here:
ALL
http://freebase-search.freebaseapps.com/?filter=(all+type%3A%2Feducation%2Fe...
and
PART OF
http://freebase-search.freebaseapps.com/?filter=(all+type%3A%2Feducation%2Fe...
Looking at the Wikidata API, this query syntax does not provide additional property (CLAIM) details:
https://www.wikidata.org/w/api.php?action=wbsearchentities&search=Valve&...
I would ideally like to have a way to output STATEMENTS or CLAIMS and their values. An ALL CLAIMS parameter, as well as providing which CLAIMS perhaps separated by | pipe.
Is there a way to do so now with the current implementation somehow ?
Thanks in advance, Thad +ThadGuidry https://www.google.com/+ThadGuidry
It seems ideally that Wikibase needs a few underpinnings in place before extending the API in further directions.
One would be a way to mark a Property as being "disambiguating", to use a Freebase parlance.
For instance, https://www.wikidata.org/w/api.php?action=wbgetentities&ids=P856 The property that has a label of "official website url" is an important disambiguating property. Unfortunately, there does not seem to be that marker that tells me if certain properties are useful to disambiguate between similar entities.
I would like to see Wikibase extended so that individual Properties could be marked as being "disambiguating" or "rather important".
Futhermore, the wbgetclaims action should also be able to use this new proposed parameter to return only disambiguating properties (instead of the default all properties) like so:
https://www.wikidata.org/w/api.php?action=wbgetclaims&entity=Q1439&r...
Thoughts ?
Thad +ThadGuidry https://www.google.com/+ThadGuidry
And so after some digging, and lack of responses on this thread, I finally find the WORK IN PROGRESS for the Wikidata team and their task of creating a better API to mimic the Freebase API and possibly re-use the Freebase query editor:
https://phabricator.wikimedia.org/T85181
I just wonder how I can get involved with helping and testing that ?
Thad +ThadGuidry https://www.google.com/+ThadGuidry
<quote name="Thad Guidry" date="2015-01-06" time="19:59:18 -0600">
And so after some digging, and lack of responses on this thread,
Hi Thad!
I'm worried that the relevant people from the Wikidata/Wikibase project just aren't seeing your messages on this mailing list. I'm cc'ing here the wikidata list.
For those on the Wikidata list, see the full thread here: https://lists.wikimedia.org/pipermail/mediawiki-api/2015-January/003454.html
Best,
Greg
On Wed, Jan 7, 2015 at 5:31 AM, Greg Grossmeier greg@wikimedia.org wrote:
<quote name="Thad Guidry" date="2015-01-06" time="19:59:18 -0600"> > And so after some digging, and lack of responses on this thread,
Hi Thad!
I'm worried that the relevant people from the Wikidata/Wikibase project just aren't seeing your messages on this mailing list. I'm cc'ing here the wikidata list.
For those on the Wikidata list, see the full thread here: https://lists.wikimedia.org/pipermail/mediawiki-api/2015-January/003454.html
Thanks, Greg!
Hey Thad,
It takes us a bit more than a few hours to reply especially over the European night ;-) To your questions: There are two fundamental things here. * Number one: Creating a query service. This work is on-going now and tracked on this workboard: https://phabricator.wikimedia.org/project/board/891/ Here input on what kinds of queries you want to run against Wikidata data would be most useful. This is things like "give me all countries in Europe" and so on. * Number two: Getting back information about one particular item or property via Wikidata's API. This would be things like "for Q64 give me the value for P6" (to get the mayor of Berlin). There it'd be most helpful to get a list of things you'd like to (optionally) see in the API response. I take it you want not only the QID of the result but also its label?
Cheers Lydia
Hi Lydia,
It's more than that. I can get labels just fine with &props=labels
Ideally there were be a Number 3.... a reconcile service, or an API that can be USED as a reconcile service.
Given a search string of "Paris", let's say...
1. Return some disambiguating properties and their labels and values. For reconciling purposes, you don't want to deal with codes like P12345 but instead a human understandable description of the property. a. Allow the output of the information returned to be expanded or reduced by some parameter values that I mentioned as OUTPUT. b. Allow the use of a (disambiguator) parameter to output only the disambiguating properties. (disambiguating properties are those that are most important when comparing A = B and given a type). In Freebase API, we had the option of this as shown here: http://freebase-search.freebaseapps.com/?query=Texas&output=(disambiguat...
The current "disambiguator" with Wikidata is actually the "descriptions". Wikidata does not flag or mark properties like P856 (official site) as a "disambiguating property", an important property. Freebase does however. It would be nice for Wikidata to begin work on having a disambiguating property flag (boolean Y/N) like Freebase does.
The closest starting point for a Reconcile API with the current API structure that I can see is hacking a bit on this one: https://www.wikidata.org/w/api.php?action=wbgetentities&sites=enwiki&...
Btw, that closest starting point, only outputs 1 entity for "Paris" in the enwiki... where's Paris, Texas ?
Thad +ThadGuidry https://www.google.com/+ThadGuidry
On 01/07/2015 09:02 AM, Thad Guidry wrote:
The closest starting point for a Reconcile API with the current API structure that I can see is hacking a bit on this one: https://www.wikidata.org/w/api.php?action=wbgetentities&sites=enwiki&...
Btw, that closest starting point, only outputs 1 entity for "Paris" in the enwiki... where's Paris, Texas ?
Have you tried using wbsearchentities[1]?
[2] is able to find both Paris, France and Paris, Texas.
[1] https://www.wikidata.org/w/api.php?modules=wbsearchentities [2] https://www.wikidata.org/w/api.php?action=wbsearchentities&search=Paris&...
-- Legoktm
Yes I did try wbsearchentities, and your right, it returns more via a search operator. The problem with wbsearchentities is that it is limited and cannot additionally pipe output for the claims information (ideally important claims only, disambiguating claims/properties)
Thad +ThadGuidry https://www.google.com/+ThadGuidry
mediawiki-api@lists.wikimedia.org