Hi Lydia,
Two questions:
* Is it possible to see if an added statement was suggested to the user?
* * Do you have some kind of versioning for the UI, to see if features
you add have a positive effect on the way Wikidata is used?
I'm not familiar with the tag system, but it looks like it can be
On Wed, Jul 2, 2014 at 12:40 PM, Lukas Benedix
bene...@zedat.fu-berlin.de wrote:
Hi Lydia,
Two questions:
* Is it possible to see if an added statement was suggested to the user?
Not currently and I don't think it'd be trivial to do unfortunately.
* * Do you have some kind of versioning
Markus Krötzsch mar...@semantic-mediawiki.org writes:
I guess the new property
suggester rather errs on the other side, being tricked into suggesting
very frequent properties even in places that don't need them.
I fund some, most notably Date of death for living people which is
likely
On 02/07/14 16:29, David Cuenca wrote:
On Tue, Jul 1, 2014 at 11:07 PM, Markus Krötzsch
mar...@semantic-mediawiki.org mailto:mar...@semantic-mediawiki.org
wrote:
My hope is that with my other suggestion (using P31 values as
features to correlate with), the property suggester will
Hey folks :)
We have just deployed the entity suggester. This helps you with
suggesting properties. So when you now add a new statement to an item
it will suggest what should most likely be added to that item. One
example: You are on an item about a person but it doesn't have a date
of birth yet.
On 1 July 2014 20:20, Lydia Pintscher lydia.pintsc...@wikimedia.de wrote:
We have just deployed the entity suggester. This helps you with
suggesting properties. So when you now add a new statement to an item
it will suggest what should most likely be added to that item. One
example: You are on
We still need to tweak it a bit here and there, yeah. We're working on
that right now. Also it will get smarter as more statements are added
to items.
Even with some somewhat off suggestions this will be a wonderful tool.
Thank you to everyone who worked on making this happen! This really
is
On Tue, Jul 1, 2014 at 9:52 PM, Derric Atzrott
datzr...@alizeepathology.com wrote:
We still need to tweak it a bit here and there, yeah. We're working on
that right now. Also it will get smarter as more statements are added
to items.
Even with some somewhat off suggestions this will be a
On 01/07/14 21:47, Lydia Pintscher wrote:
On Tue, Jul 1, 2014 at 9:44 PM, Andy Mabbett a...@pigsonthewing.org.uk wrote:
On 1 July 2014 20:20, Lydia Pintscher lydia.pintsc...@wikimedia.de wrote:
We have just deployed the entity suggester. This helps you with
suggesting properties. So when you
I noticed that sometimes it is a bit sluggish when showing the suggestions,
maybe it is my network, no idea. And it would be nice if it could suggest
the three basic properties (instance of, sublcass of, part of) when the
item is empty and suggest further properties based on that initial value,
On 01/07/14 22:14, Markus Krötzsch wrote:
...
(2) Grade I listed building
http://tools.wmflabs.org/wikidata-exports/miga/?classes#_cat=Classes/Id=Q15700818
Related properties: English Heritage list number, masts, Minor Planet
Center observatory code, home port, coordinate location, OS grid
Markus, could your algorithm work together with human direction? Like, if
we entered which properties are common for a class, and then a user creates
an instance of that class, would the algorithm be able to sort those
properties based on how often they appear on the database?
Thanks,
Micru
On
On 01/07/14 22:43, Bene* wrote:
Am 01.07.2014 22:23, schrieb Markus Krötzsch:
P.S. One weakness of my algorithm you can already see: it has troubles
estimating the relevance of very rare properties, such as Minor
Planet Center observatory code above. A single wrong annotation may
then lead to
13 matches
Mail list logo
