Actually, since Wikidata allows now properties on properties, one might easily create an item "Disambiguating property" and then make a claim "instance of - Disambiguating property" on the relevant property. there is no need for any extra implementation work.
Hi Lydia,It's more than that. I can get labels just fine with &props=labelsIdeally 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=(disambiguator)&limit=100&scoring=entity&lang=enThe 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:Btw, that closest starting point, only outputs 1 entity for "Paris" in the enwiki... where's Paris, Texas ?_______________________________________________Thad
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l