[Wikidata-l] Hello
Sent from my iPad ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
[Wikidata-l] Hello from Adam!
Hi! I'm Adam. I have just started working at WMDE on Wikidata which is contributing towards my placement year at University in the UK. I will be around for at least the next 6 months which I am sure will be great! I'm going to be working on lots of bits and pieces which I hope will keep everyone happy including usability testing, bug fixing and triage, analysis of usage patterns, api stuff and communication (among others) ! -- Adam ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from Adam!
2013/7/1 Adam Shorland adam.shorl...@wikimedia.de: Hi! I'm Adam. I have just started working at WMDE on Wikidata which is contributing towards my placement year at University in the UK. I will be around for at least the next 6 months which I am sure will be great! I'm going to be working on lots of bits and pieces which I hope will keep everyone happy including usability testing, bug fixing and triage, analysis of usage patterns, api stuff and communication (among others) ! Welcome Adam, I'm sure you will enjoy a lot your work with the Wikidata team. Cristian ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from Adam!
Il 01/07/2013 16:55, Adam Shorland ha scritto: Hi! I'm Adam. I have just started working at WMDE on Wikidata which is contributing towards my placement year at University in the UK. I will be around for at least the next 6 months which I am sure will be great! I'm going to be working on lots of bits and pieces which I hope will keep everyone happy including usability testing, bug fixing and triage, analysis of usage patterns, api stuff and communication (among others) ! -- Adam Welcome Adam! Vito ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from Adam!
Welcome :) 2013/7/1 Vito vituzzu.w...@gmail.com Il 01/07/2013 16:55, Adam Shorland ha scritto: Hi! I'm Adam. I have just started working at WMDE on Wikidata which is contributing towards my placement year at University in the UK. I will be around for at least the next 6 months which I am sure will be great! I'm going to be working on lots of bits and pieces which I hope will keep everyone happy including usability testing, bug fixing and triage, analysis of usage patterns, api stuff and communication (among others) ! -- Adam Welcome Adam! Vito ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l -- *Harold A. Hidalgo* Editorial Hidalgo Ediciones. ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
On 4/18/12 3:40 AM, Nicolas Torzec wrote:
Hi,
+1 for a wiki/FAQ describing the Wikipedia ecosystem and the relationships
between Wikidata and the other semantic projects around Wikipedia. This is a
legitimate question for the general public and the press. And it's also
probably useful for many persons in this field, as illustrated in this thread.
We could start with a general overview of Wikipedia and its semantic
ecosystem, as proposed by Kingsley.
Then we could have a summary of each project, with a highlight of its key
difference with Wikipedia, Wikidata and other projects.
And we could finish with a table summarizing the goal and difference of each
project, with links to project pages
Or is it too verbose? (in which case we might just want the introduction and
the final table...)
-Nicolas.
So we have this rough draft categorization:
Content Consumers Structured Data Transformers:
1. Freebase
2. DBpedia .
Data Wikis:
1. Freebase
2. Wikidata
*DBpedia isn't a Data Wiki because edits occur via the Wikipedia content
Wiki*
Data Wiki Platforms:
1. OntoWiki
2. Semantic MediaWiki.
Content Wikis:
1. Wikipedia
Content Wiki Platforms:
1. MediaWiki
2. Other Wiki platforms .
Kingsley
On Apr 17, 2012, at 1:51 PM, Kingsley Idehen wrote:
On 4/17/12 4:27 PM, Lydia Pintscher wrote:
On Tue, Apr 17, 2012 at 10:23 PM, Kingsley Idehen
kide...@openlinksw.com wrote:
On 4/17/12 11:32 AM, Dario Taraborelli wrote:
Shall we create a Wikidata vs {Freebase, DBpedia, YAGO} comparison table
on meta (or enwiki)? There's a lot of valuable information in this thread
(and I was not familiar with YAGO – thanks Fabian) but it's hardly readable.
We would do a huge favor to the press and the non-technical community if we
had a single place where the differences are documented. Currently, there's
only one page about the relation between Wikidata and DBpedia. [1]
Lydia, any thoughts?
Not a versus style table. That sends the wrong signals when these services
are fundamentally complimentary .
Yes. I'd prefer a short text - something we can add to the existing
FAQ. (That's also what I have so far.)
Cheers
Lydia
How about fleshing this out?
[WikiData] -- (ProducingbetterRefStructuredDataFor) -- [Wikipedia] [Rest of
the Web] .
[Freebase] -- (consumingContentFrom) -- [Wikipedia].
[DBpedia] -- (consumingContentFrom) -- [Wikipedia].
[DBpedia] -- (crossReferences) -- [Freebase] .
[Freebase] -- (crossReferences) -- [DBpedia] .
[DBpedia] -- (crossReferences) -- [YAGO] .
[YAGO] -- (crossReferences) -- [DBpedia] .
[WikiData] -- (leverages) -- [All of the Above] .
++
--
Regards,
Kingsley Idehen
Founder CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
--
Regards,
Kingsley Idehen
Founder CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen
smime.p7s
Description: S/MIME Cryptographic Signature
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
On Wed, Apr 18, 2012 at 3:50 PM, Ted Thibodeau Jr tthibod...@openlinksw.com wrote: One element I see missing from (or at least, unclear in) the discussion thus far, is how corrections or other changes are made to the data therein, and how changes made in one set are fed (back) to the others. In other words -- 1. When an error is discovered in data on service x, where are edits made to correct that data? 2. If edits are made locally (on service x) to content which originated on another service (y), do those edits also get applied to the original source, and if so, how (e.g., automatically by service x; manually by the user; manually by service x admin team; etc.)? I think information like this is needed throughout, and will help a lot in demonstrating the complementary nature of these various services. DBpedia content, for instance, is not edited directly, but gets all its changes by digesting edits made to Wikipedia. Freebase also digests changes made to Wikipedia (but it's not clear to me exactly how these are then acted on), but is also edited directly -- and I don't see a mechanism that routes such direct Freebase edits back to Wikipedia (or elsewhere). Regards, Ted Editing will be possible in Wikidata directly. These changes will be visible in whatever gets its data from Wikidata, like Wikipedia. The rest is a bit outside the scope of this list. Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Community Communications for Wikidata Wikimedia Deutschland e.V. Obentrautstr. 72 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985. ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
On Tue, Apr 17, 2012 at 4:27 PM, Lydia Pintscher
lydia.pintsc...@wikimedia.de wrote:
On Tue, Apr 17, 2012 at 10:23 PM, Kingsley Idehen
kide...@openlinksw.com wrote:
On 4/17/12 11:32 AM, Dario Taraborelli wrote:
Shall we create a Wikidata vs {Freebase, DBpedia, YAGO} comparison table
on meta (or enwiki)?
Not a versus style table. That sends the wrong signals when these services
are fundamentally complimentary .
Yes. I'd prefer a short text - something we can add to the existing
FAQ. (That's also what I have so far.)
I actually like tables myself and don't see them as being adversarial,
but I'm happy to contribute to the comparison in whatever form it
takes.
Having a matrix/table: a) focuses people on choosing a few important
dimensions to summarize and b) makes any holes in the comparison
matrix obvious so they can be filled in (which is much harder when
parsing text).
Tom
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
On 4/18/12 10:25 AM, Tom Morris wrote:
On Tue, Apr 17, 2012 at 4:27 PM, Lydia Pintscher
lydia.pintsc...@wikimedia.de wrote:
On Tue, Apr 17, 2012 at 10:23 PM, Kingsley Idehen
kide...@openlinksw.com wrote:
On 4/17/12 11:32 AM, Dario Taraborelli wrote:
Shall we create a Wikidata vs {Freebase, DBpedia, YAGO} comparison table
on meta (or enwiki)?
Not a versus style table. That sends the wrong signals when these services
are fundamentally complimentary .
Yes. I'd prefer a short text - something we can add to the existing
FAQ. (That's also what I have so far.)
I actually like tables myself and don't see them as being adversarial,
but I'm happy to contribute to the comparison in whatever form it
takes.
Having a matrix/table: a) focuses people on choosing a few important
dimensions to summarize and b) makes any holes in the comparison
matrix obvious so they can be filled in (which is much harder when
parsing text).
Tom
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Tom,
To clarify the context of my comment.
I meant versus is adversarial. I have nothing against tables and the
coherence of tabular style presentation.
--
Regards,
Kingsley Idehen
Founder CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen
smime.p7s
Description: S/MIME Cryptographic Signature
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
Hi, thanks for all of these information! I wanted to clarify the quality guarantee in YAGO. It is true that we did not evaluate every statement individually. Rather, we proceeded as follows: For each relation in YAGO, we have taken a random sample, and evaluated it manually (wrt Wikipedia). From the ratio of correct statements on the sample, we have used statistic techniques to estimated the ratio of correct statements for the whole of YAGO. This ratio will usually be lower than the ratio on the sample. Thus, more precisely, the guarantee reads: With a probability of 95%, the ratio of correct statements for actedInMovie is in the interval 97.36%+/-2.64%. I also wanted to ask again on the relationship between Freebase and Wikidata: Freebase was bootstrapped from the infoboxes of Wikipedia, but I think its main selling point is that volunteers can add and correct data. Thus, my understanding is that, both in Wikidata and in Freebase, volunteers would fill up structured, factual information. Is that right? My intuition is that Wikidata will have a more principled approach, because it can build on the Wikipedia/Wikimedia culture. Other comments are appreciated. Thanks Fabian ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
On 4/17/12 8:33 AM, Fabian M. Suchanek wrote: I also wanted to ask again on the relationship between Freebase and Wikidata: Freebase was bootstrapped from the infoboxes of Wikipedia, but I think its main selling point is that volunteers can add and correct data. Thus, my understanding is that, both in Wikidata and in Freebase, volunteers would fill up structured, factual information. Is that right? My intuition is that Wikidata will have a more principled approach, because it can build on the Wikipedia/Wikimedia culture. Other comments are appreciated. Yes, in a nutshell. Freebase is a kind of Data Wiki just like Wikidata. Folks will create and manage data objects in both data spaces. Mutual benefits will arise from object co- and cross-references across these data spaces, thanks to the Web :-) I see something like this: [WikiData] -- (ProducingbetterRefStructuredDataFor) -- [Wikipedia] [Rest of the Web] . [Freebase] -- (consumingContentFrom) -- [Wikipedia]. [DBpedia] -- (consumingContentFrom) -- [Wikipedia]. [DBpedia] -- (crossReferences) -- [Freebase] . [Freebase] -- (crossReferences) -- [DBpedia] . [DBpedia] -- (crossReferences) -- [YAGO] . [YAGO] -- (crossReferences) -- [DBpedia] . [WikiData] -- (leverages) -- [All of the Above] . ++ -- Regards, Kingsley Idehen Founder CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen smime.p7s Description: S/MIME Cryptographic Signature ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
On Mon, Apr 16, 2012 at 5:19 PM, Kingsley Idehen kide...@openlinksw.com wrote: On 4/16/12 2:54 PM, Tom Morris wrote: - the refresh cycle is every couple of weeks (ie much faster than DBpedia but much slower than DBpedia live) Why do you make the comment above? Are you not aware of the DBpedia-Live editions have existed for a few years now? I think my text that you quoted answers the question since I reference Live -- or do I get points off for incorrect capitalization/punctuation? three months two weeks minutes DBpedia Freebase DBpedia-Live (phew! spelled it correctly this time) By my calculations though, availability is actually 10 months, not a few years. http://blog.aksw.org/2011/official-dbpedia-live-release/ On Tue, Apr 17, 2012 at 8:33 AM, Fabian M. Suchanek f.m.sucha...@gmail.com wrote: I also wanted to ask again on the relationship between Freebase and Wikidata: Freebase was bootstrapped from the infoboxes of Wikipedia, Wikipedia based data from infoboxes is updated on a regular basis. It wasn't just a one time bootstrap. but I think its main selling point is that volunteers can add and correct data. Thus, my understanding is that, both in Wikidata and in Freebase, volunteers would fill up structured, factual information. Is that right? I outlined most of the major differences that come to mind. I don't think there's any one particular selling point and, in particular, the Freebase team has never really attempted to do much in the way of selling at all. I don't really think that there's any overlap or competition between the two projects. If Wikidata is successful, Freebase rips out their infoboxes parsers and gets cleaner Wikipedia data to import with less effort. My intuition is that Wikidata will have a more principled approach, because it can build on the Wikipedia/Wikimedia culture. To the extent that the Wikidata project is unsuccessful in changing the current Wikipedia culture, they'll inherit both the good and bad points of the existing culture. Personally, I could do with a few less deletionists and petty tyrants ruling their corner of Wikipedia. Tom ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
On Tue, Apr 17, 2012 at 5:32 PM, Dario Taraborelli
dtarabore...@wikimedia.org wrote:
Shall we create a Wikidata vs {Freebase, DBpedia, YAGO} comparison table on
meta (or enwiki)? There's a lot of valuable information in this thread (and I
was not familiar with YAGO – thanks Fabian) but it's hardly readable. We
would do a huge favor to the press and the non-technical community if we had
a single place where the differences are documented. Currently, there's only
one page about the relation between Wikidata and DBpedia. [1]
Lydia, any thoughts?
Yes, definitely. I've started working on that but it's just a start
and I need some more input from people before this is in a publishable
state. If anyone wants to help please let me know.
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Community Communications for Wikidata
Wikimedia Deutschland e.V.
Obentrautstr. 72
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
On Tue, Apr 17, 2012 at 10:23 PM, Kingsley Idehen
kide...@openlinksw.com wrote:
On 4/17/12 11:32 AM, Dario Taraborelli wrote:
Shall we create a Wikidata vs {Freebase, DBpedia, YAGO} comparison table
on meta (or enwiki)? There's a lot of valuable information in this thread
(and I was not familiar with YAGO – thanks Fabian) but it's hardly readable.
We would do a huge favor to the press and the non-technical community if we
had a single place where the differences are documented. Currently, there's
only one page about the relation between Wikidata and DBpedia. [1]
Lydia, any thoughts?
Not a versus style table. That sends the wrong signals when these services
are fundamentally complimentary .
Yes. I'd prefer a short text - something we can add to the existing
FAQ. (That's also what I have so far.)
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Community Communications for Wikidata
Wikimedia Deutschland e.V.
Obentrautstr. 72
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
On 4/17/12 4:27 PM, Lydia Pintscher wrote:
On Tue, Apr 17, 2012 at 10:23 PM, Kingsley Idehen
kide...@openlinksw.com wrote:
On 4/17/12 11:32 AM, Dario Taraborelli wrote:
Shall we create a Wikidata vs {Freebase, DBpedia, YAGO} comparison table
on meta (or enwiki)? There's a lot of valuable information in this thread
(and I was not familiar with YAGO – thanks Fabian) but it's hardly readable.
We would do a huge favor to the press and the non-technical community if we
had a single place where the differences are documented. Currently, there's
only one page about the relation between Wikidata and DBpedia. [1]
Lydia, any thoughts?
Not a versus style table. That sends the wrong signals when these services
are fundamentally complimentary .
Yes. I'd prefer a short text - something we can add to the existing
FAQ. (That's also what I have so far.)
Cheers
Lydia
How about fleshing this out?
[WikiData] -- (ProducingbetterRefStructuredDataFor) -- [Wikipedia]
[Rest of the Web] .
[Freebase] -- (consumingContentFrom) -- [Wikipedia].
[DBpedia] -- (consumingContentFrom) -- [Wikipedia].
[DBpedia] -- (crossReferences) -- [Freebase] .
[Freebase] -- (crossReferences) -- [DBpedia] .
[DBpedia] -- (crossReferences) -- [YAGO] .
[YAGO] -- (crossReferences) -- [DBpedia] .
[WikiData] -- (leverages) -- [All of the Above] .
++
--
Regards,
Kingsley Idehen
Founder CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen
smime.p7s
Description: S/MIME Cryptographic Signature
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
From: JFC Morfin jef...@jefsey.com Thank you for this detailed explanation. How do you see the integration/impact of Wikidata on both projects? My intuition is that the impact could be mutual: * for YAGO and DBpedia, the impact would be immediate, because Wikidata could essentially provide cleaner infobox data for these projects. Yet, we have to see how Wikidata will position itself to Freebase, which seems to pursue a similar goal: http://en.wikipedia.org/wiki/Freebase (If you have thoughts on distinguishing Wikidata from Freebase, we'd be happy to know) * for Wikidata, there could be some leverage in the ontologies as well, possibly for bootstrapping. - YAGO, e.g., has mappings of infobox data to relations with domains and ranges, with a quality guarantee. One naive idea is that these could contribute to filling up Wikidata initially, because it seems easier for humans to correct or complete data than to insert it from scratch. - Another aspect is that YAGO connects the Wikipedia categories and pages to WordNet, the major digital lexicon of English (http://wordnet.princeton.edu/). This could contribute a strict semantic typing / class hierarchy / taxonomy to Wikidata, which is so far absent in Wikipedia. - Last, YAGO has the connection to Geonames (providing data about geographical entities), and also the connection to the Universal Wordnet (providing translations of class names and entity names to 200 other languages -- basically a cleaned and expanded version of the Wikipedia interlanguage links). - DBpedia, too, could contribute, because its hub position in the cloud of linked data connects it to many other resources. Cheers Fabian ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
On Mon, Apr 16, 2012 at 10:54 AM, Fabian M. Suchanek f.m.sucha...@gmail.com wrote: From: JFC Morfin jef...@jefsey.com Thank you for this detailed explanation. How do you see the integration/impact of Wikidata on both projects? My intuition is that the impact could be mutual: * for YAGO and DBpedia, the impact would be immediate, because Wikidata could essentially provide cleaner infobox data for these projects. Yet, we have to see how Wikidata will position itself to Freebase, which seems to pursue a similar goal: http://en.wikipedia.org/wiki/Freebase (If you have thoughts on distinguishing Wikidata from Freebase, we'd be happy to know) I don't speak for Freebase, but I view Freebase, DBpedia, and YAGO as all occupying comparable positions relative to Wikipedia/Wikidata. They currently attempt to reverse engineer structured data out of Wikipedia infoboxes and if Wikidata is successful in providing the data source for the Wikipedia infoboxes, it'll eliminate a lot of troublesome, error-prone parsing code. Some of the ways that Freebase is different include: - it's editable by anyone, so you don't need to go back to Wikipedia to correct mistakes. - it doesn't have a notability requirement like Wikipedia. If it's factual and non-spammy, you can include it. - infobox mappings aren't public and can only be modified by Google employees - a relatively small number of popular infoboxes are mined (nowhere near DBpedia's coverage) - the refresh cycle is every couple of weeks (ie much faster than DBpedia but much slower than DBpedia live) - it includes a large amount of non-Wikipedia data from MusicBrainz, OpenLibrary, Geonames, etc, as well as being linked to a number of other sources of strong identifiers such as the New York Times, IMDB, NNDB, U.S. Library of Congress Name Authority File and Subject Headings, etc. As far as positioning between Wikidata and Freebase goes, there's really no way that Freebase (or any other non-Wikimedia Foundation effort) could ever compete with Wikidata in the context of providing data to Wikipedia. The Wikipedia culture is just too insular. Instead I would expect Freebase to stop parsing infoboxes and consume data directly from Wikidata in the same way that I would expect DBpedia, YAGO and other consumers to. Before that happens though, Wikidata not only needs to get the technical infrastructure in place, but also change the culture of Wikipedia editors so that they're not anti-data and care about the semantics as well as the presentation of the information. A lot of today's quality problems are social, not technical. - YAGO, e.g., has mappings of infobox data to relations with domains and ranges, with a quality guarantee. Guarantee? My understanding of the previous post was that a very small sample of YAGO data had been measured for precision (with good results), not that there was 100% curation or any type of quality guarantee. Freebase has a stated 99% quality goal, but actual quality (as well as coverage) varies greatly from domain to domain. Tom ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
On 4/16/12 2:54 PM, Tom Morris wrote: - the refresh cycle is every couple of weeks (ie much faster than DBpedia but much slower than DBpedia live) Why do you make the comment above? Are you not aware of the DBpedia-Live editions have existed for a few years now? Fundamentally, Freebase addresses some of what DBpedia covers and some of what Wikidata (a Data Wiki) covers. Of course, all of these -- plus YAGO -- are inherently mutually beneficial. Links: 1. http://live.dbpedia.org/LiveStats/ -- DBpedia-Live hosted by University of Leipzig. 2. http://dbpedia-live.openlinksw.com/live/ -- DBpedia-Live edition we host . -- Regards, Kingsley Idehen Founder CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen smime.p7s Description: S/MIME Cryptographic Signature ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
I meanwhile found a public accessible link to your publication: http://www.mpi-inf.mpg.de/yago-naga/yago/publications/aij.pdf in which you write: However, in contrast to the original YAGO, the methodology for building YAGO2 (and also maintaining it) is systematically designed top-down with the goal of integrating entity-relationship-oriented facts with the spatial and tempo- ral dimensions. To this end, we have developed an extensible approach to fact extraction from Wikipedia and other sources, and we have tapped on specific inputs that contribute to the goal of enhancing facts with spatio-temporal scope. Moreover, we have developed a new representation model, coined SPOTL tuples (SPO + Time + Location), which can co-exist with SPO triples, but provide a much more convenient way of browsing and querying the YAGO2 knowl- edge base. etc. page 3 so it seems one special feature is the explicit treatment of space and time, which sounds interesting. So I would like make some of my questions more precise YAGO has about 100 manually defined relations, such as wasBornOnDate, locatedIn and hasPopulation. Categories and infoboxes can be exploited to deliver instances of these relations. (p.3) ... The new YAGO2 architecture is based on declarative rules that are stored in text files. -Is there a wiki or some other public accessible place for those like the mapping wiki of dbpedia? -what do you do if infoboxes change? -How do you treat microformats? Instead of seeing only SPO triples and thus having to perform an explicit de-reification join for associated meta-facts, the user should see extended 5-tuples where each fact already includes its associated temporal and spatial information. We refer to this view of the data as the SPOTL view: SPO triples augmented by Time and Location. We also discuss a further optional extension into SPOTLX 6-tuples where the last component offers keywords or key phrases from the conteXt of sources where the original SPO fact occurs.(p. 20) It is not yet fully clear to me how your concept go together with other concepts to include contexts like with named graphs or with the inclusion of context-ontologies within formats like JSON-LD, eventually that would need a longer discussion, are you planning to set up a wiki page on datawiki, like for example there is one for JSON-LD: http://meta.wikimedia.org/wiki/Talk:Wikidata/Data_model/JSON ? Is it possible to extract the Yago queries in some RDF serialization format?___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
-- Nadja Kutz wrote Is it possible to briefly explain the major differences between DBpedia and the Yago Knowledge graph? Both projects aim to extract a so-called ontology from Wikipedia. An ontology in this sense is a graph (= a kind of net), in which the nodes are entities (like Albert Einstein, or the city of Ulm) and the links between the nodes are relationships (like wasBornIn). See here for an example: http://www.mpi-inf.mpg.de/departments/ontologies/areas/index.html For this purpose, both projects use the structured information of Wikipedia, i.e., its category system and its infoboxes. Both projects have extracted a graph of several million nodes, and dozens of millions of links between them. Seen this way, the projects go in the same direction as what Wikidata aims to do, but in an automated fashion. Both projects share the same goal, but have different foci: * YAGO has a set of around 100 relationships and maps Wikipedia infobox attributes to them. DBpedia, in contrast, has two systems - one system, in which each Wikipedia infobox attribute becomes a relationship. This set of data is rather noisy, but very exhaustive. - another system, in which relationships are defined and mapped from infobox attributes by a community of voluteers. The differences between these two systems are summarized here in Chapter 10.3 http://www.mpi-inf.mpg.de/yago-naga/yago/publications/aij.pdf * DBpedia is the hub of the linked data cloud. YAGO is also in this cloud, but not as central as DBpedia. * YAGO attaches time and space information to many of its entities, i.e., it knows when and where certain facts happened, and integrates this information with data from Geonames. This aspect is less prominent in DBpedia. * YAGO has traditionally put much emphasis on logical constraint checking, type checking, and a strong type hierarchy -- all in order to maintain a high precision of the data. DBpedia, in contrast, imports one of its type hierarchies from YAGO, and builds its own, flatter, type hierarchy through a community of volunteers. * YAGO has been evaluated manually, thus attaching a probabilistic precision value to each of its relations. That is, for the relation actedInMovie, e.g., we know that 97% of the statements are correct. Details are here: http://www.mpi-inf.mpg.de/yago-naga/yago/statistics.html For DBpedia, there is no such analysis to our knowledge. * Both ontologies have a surprisingly small overlap of data and instances, if mapped naively, see Chapter 5.2.3 in http://suchanek.name/work/publications/iswc2011.pdf ... but a larger overlap if mapped in a more sophisticated way, see Section 6.4 in http://suchanek.name/work/publications/vldb2012.pdf * there are certainly a number of more differences, which I may not know or I may have overseen, please feel free to add. what is the www conference ? The WWW conference is a scientific conference in computer science on the newest developments of the Web. It is in Lyon this year: http://www2012.wwwconference.org Cheers Fabian -- Fabian online: http://suchanek.name ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
Hello Fabian, Is it possible to briefly explain the major differences between DBpedia and the Yago Knowledge graph? what is the www conference ? nad ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
[Wikidata-l] Hello from the YAGO team
Dear Wikidata team, I am writing on behalf of the YAGO team at the Max Planck Institute for Informatics in Saarbruecken [1]. We have heard about the Wikidata project, and we are very excited to learn that you aim to launch a free knowledge base in the spirit of Wikipedia. We would like to get in touch with you -- also to see whether or how we could help on the long run. Let me briefly tell you what we have on our side: As you might know, YAGO is knowledge graph that has been extracted automatically from the infoboxes and categories of Wikipedia. We have evaluated YAGO manually and achieved a precision of 95%, meaning that statistically speaking, only 5 out of 100 statements in the knowledge graph are extracted wrongly. We also have a link of the Wikicategories to the WordNet taxonomy (again with 95% precision), and type checking methods for the extracted statements. Should these things ever be useful to you, we would be happy to help. I will be at the WWW conference next week. In case some of you are there, too, I'd be happy to get in touch to learn more about your current work. Thanks Fabian [1] http://yago-knowledge.org -- Thanks Fabian -- Fabian online: http://suchanek.name ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Hello from the YAGO team
On Fri, Apr 13, 2012 at 3:50 PM, Fabian M. Suchanek f.m.sucha...@gmail.com wrote: Dear Wikidata team, I am writing on behalf of the YAGO team at the Max Planck Institute for Informatics in Saarbruecken [1]. We have heard about the Wikidata project, and we are very excited to learn that you aim to launch a free knowledge base in the spirit of Wikipedia. We would like to get in touch with you -- also to see whether or how we could help on the long run. Let me briefly tell you what we have on our side: As you might know, YAGO is knowledge graph that has been extracted automatically from the infoboxes and categories of Wikipedia. We have evaluated YAGO manually and achieved a precision of 95%, meaning that statistically speaking, only 5 out of 100 statements in the knowledge graph are extracted wrongly. We also have a link of the Wikicategories to the WordNet taxonomy (again with 95% precision), and type checking methods for the extracted statements. Should these things ever be useful to you, we would be happy to help. Great to hear. I will be at the WWW conference next week. In case some of you are there, too, I'd be happy to get in touch to learn more about your current work. Denny Vrandečić will be there for Wikidata. Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Community Communications for Wikidata Wikimedia Deutschland e.V. Obentrautstr. 72 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985. ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
