22
past, present & future DBpedia Community Meeting 25.06.15 Poznan

DBpedia past, present & future

Embed Size (px)

Citation preview

Page 1: DBpedia past, present & future

past, present & future

DBpedia Community Meeting 25.06.15 Poznan

Page 2: DBpedia past, present & future

2007

2007

2014

???

Page 3: DBpedia past, present & future

Get me all soccer players, who played as goalkeeper for a club that has a stadium with more than 40.000 seats and who are born in a country with more than 10 million inhabitants

Page 4: DBpedia past, present & future

Structure in Wikipedia

bnjmbn

...

Page 5: DBpedia past, present & future

Infoboxes

???

Page 6: DBpedia past, present & future

How it all started

- 2006 - Sören Auer (busy with his PhD) asking people: “Wikipedia fact tables look like triples, don’t you want to write some extractor?”

- 6 months later: Sören wrote the extractor himself and asked Jens Lehmann to help with writing a paper

- Chris Bizer : “We are extracting people and place information from Wikipedia too – lets join efforts and call it DBpedia.”

- Kingsley Idehen: “I need a showcase for my Virtuoso triple store.”

Page 7: DBpedia past, present & future

Infobox Extraction

Wikitext

RDF

Page 8: DBpedia past, present & future

Taking a closer look

at heterogeneity…

- DBpedia Mappings wiki

Page 9: DBpedia past, present & future

Milestones

- 2008: DBpedia Live- 2009: Scala-Based framework- 2009: Mappings wiki- 2011: Internationalization- 2011: DBpedia Spotlight- 2014: DBpedia Association (S. Hellmann)

Page 10: DBpedia past, present & future

Now

DBpedia 2014 (English):4.58 mio. entities and 583 mio. triples

131,2 mio. fact assertions (derived from infoboxes)

168,5 mio. triples representing Wikipedia structure

57,1 mio. links to external datasets

Localized DBpedia version for 125 languages, built from corresponding Wikipedia versions

12 DBpedia language chapters

Page 11: DBpedia past, present & future

Now

X

Page 12: DBpedia past, present & future
Page 13: DBpedia past, present & future

DBpedia has to evolve

- Fusion- Validation- NLP- Enterprize

Page 14: DBpedia past, present & future

Fusion

Page 15: DBpedia past, present & future

Validation

Page 16: DBpedia past, present & future

NLP

- Exploit the text…- Let different NLP tools & approaches

compete for the best quality (in a certain language)

- Need to define the interface (help needed)

Page 17: DBpedia past, present & future

Every Enterprise needs its DBpedia

- Represent common sense knowledge (DBpedia and other LOD datasets) as well as the specific enterprise knowledge

- Crystallization points for Linked Data intranets – an addition to SOA facilitating enterprise-wide data linking & integration

- Slicing & Dicing

Page 18: DBpedia past, present & future

Other ideas?

add them in http://dbpedia.org/ideas (404)

Page 20: DBpedia past, present & future

The soccer players (for the curious)

Page 21: DBpedia past, present & future

Thank you

Big thanks to Sören Auer & Markus Ackermann for slide contributions

Page 22: DBpedia past, present & future

Big thanks to Sören Auer & Markus Ackermann for slide contributions