Hi Bene,
Yes, I have played with a few of the SPARQL endpoints. Interesting things
sometimes do popup excitedly unexpected. I like those. But many assumptions
have to be made in certain corner cases. But that why I have a brain, to
make my own internal DAG whenever I need. :)
ALL,
Thanks for
In Freebase, we had bot scripts that went through and removed Lists of
Things topic entities since they are lists of entities and not useful
clumped together and normalized in a graph database.
Does Wikidata have something similar or a user review process for deletion
of these ?
Ex. List of
By this reasoning we should also delete items about categories or
disambiguation pages.
Thad Guidry, 15/06/2015 17:21:
Ex. List of tallest buildings in Wuhan -
https://www.wikidata.org/wiki/Q6642364
What's the issue here? The item doesn't actually contain any list, there
is no duplication
Federico,
As a Data Architect, I only care about individual Entities. I do not care
what Wikidata needs internal for coordination with Wikipedia, etc...
There is no contradiction...as long as Wikdata provides a good mechanism
for me to filter out non-entities. Ideally an API or Search
Am 15.06.2015 um 20:09 schrieb Thad Guidry:
Federico,
As a Data Architect, I only care about individual Entities. I do not care
what
Wikidata needs internal for coordination with Wikipedia, etc...
There is no contradiction...as long as Wikdata provides a good mechanism for
me
to
Hoi,
I have been REALLY active in adding statements with is a list of They do
have a function. They show the content of a list in Reasonator.
I do appreciate it when they are retained. They are both lists and
categories.
THanks,
GerardM
On 15 June 2015 at 17:53, Benjamin Good
Also the list entity has a function. The function of *instance of* is to
identify what a page is about. A database is built on consistency, the list
entity does do that for lists. A list is a very special type of a subject
in comparison to other articles. It isn't linked through topic type
Thad Guidry, 15/06/2015 18:11:
I think Wikidata needs to decide going forward if it will be a strict
Entity Graph...or if it will be a Big Graph of all things Wikipedia.
I understand the question, but why are the two things in contradiction?
Nemo
Am 15.06.2015 um 18:11 schrieb Thad Guidry:
In General,
I think Wikidata needs to decide going forward if it will be a strict Entity
Graph...or if it will be a Big Graph of all things Wikipedia.
Its an important question...if it decides on the latter...then just give a way
to filter out
I think this is clearly an evolutionary process. In the short term,
wikidata needs to support Wikipedia use cases as Andrew mentioned above
(thank you for the clarification). In the long term, this function and all
other functions will (in my opinion) best be served by a transition into
more and
We can create as many specialized classes as we want. That lists are more
specific than classes is not a fatality.
I think having a list about instances of a concept proves the concept is
useful, so that the class is something that could exists. Moreother if we
manually mark an item as an
Hi!
In Freebase, we had bot scripts that went through and removed Lists of
Things topic entities since they are lists of entities and not useful
clumped together and normalized in a graph database.
Why delete them? Wikidata has a number of things which are not your
standard entity - lists,
Stas,
Always agreed, it's a classification problem.
So what claims/statements do I rule out ? Or what should I only rule in
(claims/statements) when wanting to return only real entities ? Can
someone help with those negative claims/statements that I am looking for ?
So far, I only have got
13 matches
Mail list logo
