77
Open Knowledge Network A.W. Moore & R.V.Guha

Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

  • Upload
    others

  • View
    3

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Open Knowledge NetworkA.W. Moore & R.V.Guha

Page 2: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 3: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

→…

Page 4: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 5: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Google Now

Microsoft Cortana

Page 6: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Why this initiative: Closed vs Open…

Page 7: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

→…

Page 8: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Page 9: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 10: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Lessons from history

Page 11: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Open Knowledge Network

Page 12: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

• GIS• Amazon• UMLS Codes• Indexed Web Docs• CYC• wikidata• freebase• tripadvisor etc• schema.org

• Existing Entity Stores

• Architecture– Catalog– Matching Engine– Facts– Normalization

Engine• Use Cases• Risks

Page 13: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Global ID = 0xA3569B

Short Title = [Logitech Digital I/O Pen]Short Mentions

Logitech Digital IODigital IO PenLong

MentionsImages

Global ID = 0x220CCC

Short Title = [Pittsburgh]Short Mentions

Pittsburg

PITLong MentionsImages

. . .

. . .

. . .

. . .

• Existing Entity Stores

• Architecture– Catalog– Matching Engine– Facts– Normalization

Engine• Use Cases• Risks

Page 14: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

“….unlike Logi-Techs’ new digital IO stylus, which…”

Global ID = 0xA3569B with probability 0.94Global ID = 0xEEA001 with probability 0.02…

• Existing Entity Stores

• Architecture– Catalog– Matching Engine– Facts– Normalization

Engine• Use Cases• Risks

Page 15: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

“Triples” is one popular approach:

• <Banana ID>.color = <yellow ID>

• (<HSBC ID> is_a <Bank ID>)

• (<Dell XPS 13” notebook 2015 ID> has_a <2mm 12 Volt DC composite power socket ID>)

• There is and will continue to be a major intellectual war on the expressiveness of the semantics.

• Winner should be decided by use cases.

• Existing Entity Stores

• Architecture– Catalog– Matching Engine– Facts– Normalization

Engine• Use Cases• Risks

Page 16: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

“Jersey”

“NYC” “Big Apple”

• Existing Entity Stores

• Architecture– Catalog– Matching Engine– Facts– Normalization

Engine• Use Cases• Risks

Page 17: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

• Existing Entity Stores

• Architecture– Catalog– Matching Engine– Facts– Normalization

Engine• Use Cases• Risks

Question answering:Fact Questions:• [How old is vice president Pence?]• [Which Washington-based think tanks have worked on projects involving South

American trade?]• [Which building am I in? Where do I go for a taxi?]Research Questions:• [What are good things to do with kids in Pittsburgh?]• [Which Hodgkins Lymphoma treatments are covered under the Affordable Care Act

for my mother?]• [What do the cells in capillary systems of liver tumors unresponsive to sorenafib

have in common?]The right-click on a spreadsheet-column use case

A scientist or analyst wishes to canonicalize and then do joins with data she is using.Knowledge-powered machine learning

Allowing secondary and tertiary features and aggregates to be used in machine learning algorithms.

Knowledge-powered roboticsCommon sense reasoning; a robot needs to understand, not simply sense, its environment.

Knowledge powered startup and app developer ecosystemGenerally making it easier to write a useful app for domain X which needs to know about entities in domain Y (e.g. a great liver cancer app actually needs to know bus routes to treatment centers).

Page 18: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

• Existing Entity Stores

• Architecture– Catalog– Matching Engine– Facts– Normalization

Engine• Use Cases• Risks

Technical Risks• Undermerging, Overmerging, Multilevel taxonomies,

Time, Uncertainty, Provenance.• Entity stores are alive: You don’t build an entity store

once; you build a process to maintain, grow, and update a set of entities.

• Physics and Sensing: Many use cases (robotics and sensing) need to maintain information about visual, acoustic, and physics of physical-world objects.

Non-technical risks• Privacy. Very serious problem. We recommend not

including PII in such a project. There will need to be practical privacy technology in place to ask “what is the average age of women in Pittsburgh?” without having any explicit representation of all the people in Pittsburgh.

• Provenance: many major industries have their business model around obtaining facts.

• Why not leave this up to a large internet company to build? (Ans: this is bigger than Google or Apple or….)

Page 19: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Open Knowledge Network

Page 20: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Making progress: Open Data

Page 21: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Making Progress: Curated Data

Page 22: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Almost there ...

Page 23: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Page 24: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 25: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 26: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 27: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

→ →

Page 28: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Page 29: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Page 30: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 31: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Lots of interesting problems

Page 32: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 33: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Chuck Norris

Ryan, Oklahoma

March 10th 1940

birthplace

Actor

type

citizenOf

USA

birthdate

Page 34: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 35: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Concluding

Page 36: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Questions?

Page 37: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Reserve slides below (may not be needed)

Page 38: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Where we are now

More than 15m sites publishing snippets of structured data using schema.org, Facebook OGP, etc.Biggest problem --- getting publishers to publish is starting to see solutionSearch & personal assistants are killer app

Page 39: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 40: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 41: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Many challenges remain

- Only content of interest to search engines- Centralized small schema

-- Only big players consume the data

- Crawl/index is too big a barrier

Page 42: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Analogy with Web: HTML : ?

- HTML provided small set of standard terms (‘div’, ‘table’, ‘body’, etc.)

- All documents that stuck to these were understood by all browsers

- What is the equivalent here? Billions of entities ...

Page 43: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Game of the name

~1000s of terms like Actor, birthdate~10s for most sitesCommon across sites

~1b-100b terms like Chuck Norris and Ryan, Oklahama Cannot expect agreement on these Need something much more sophisticated than HTML

birthplacetype

citizenOf birthdate

spouseChuck NorrisGena O’Kelley

USA

Ryan, OKActor

March 10, 1940

Page 44: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Web Analogy: Search engines

- Search engines made web usable- Need something similar here

- Collect data from different publishers (Crawl)- Aggregate it (Index)- Serve (Ranking)

- Consumer here is a program, not human!

Page 45: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Challenges

- Crawling: hyperlinks help web crawl. - What is the analog here? - Overlay of web pages that link to datasets?

Page 46: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Challenges: Building the index

Analog of words : entitiesBuilding the index ---> large scale entity recon

Page 47: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Challenges: Ranking

Single answer vs ranked set of possible answers

Ranking could be based on authoritativeness of source

Page 48: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Representation

Simple graph representation is easy to understand

Can’t do a lot of things, e.g., timeHow rich should the KR lang be?

N-ary rels, negation, quantifiers, …Do we have to agree?

Page 49: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Representation

Hybrid representations- structured + unstructured- embeddings

Page 50: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Concluding

- Many interesting research problems

- Good news:- Lot of data already being published- First generation of apps already there- Don’t have to solve all these problems before useful

things can be done

Page 51: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 52: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Questions?

Page 53: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 54: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Deep pool of research

Page 55: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Long history of systems

Page 56: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Structured data & WebMaking structured data a first class thing on the web

Structured Data

Web server

Page 57: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

The Goal

Graph Data ModelCommon Vocabulary

birthplacetype

citizenOf birthdate

spouseChuck NorrisGena O’Kelley

USA

Ryan, OKActor

March 10, 1940

Page 58: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Timeline of efforts

Page 59: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Schema.orgWork started in August 2010. Google, Microsoft, Yahoo … Now also Apple, W3C …

Provides core vocabulary for people, places, events, offers, actions, ... Understood by the search engines

Search (structured data in search) was driving application

Page 60: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 61: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 62: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Schema.org … the numbersApprox. 1800 terms (classes + attributes)

In use by ~15 million sites Roughly 30% of pages in search index have markup ~25 ‘triples’ per page 30% growth over last 12 months

~40% of US/EU ecommerce emails (sales confirmation, reservations, etc.) use schema.org markup

Page 63: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Schema.org: Major sitesNews: Nytimes, guardian, bbc,Movies: imdb, rottentomatoes, movies.comJobs / careers: careerjet, monster, indeed, simplyhiredPeople: linkedin.com, facebookProducts: ebay, alibaba, sears, cafepress, sulit, fotoliaLocal: yelp, allmenus, urbanspoonEvents: wherevent, meetup, zillow, eventfulMusic: last.fm, soundcloud….

Page 64: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 65: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 66: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Page 67: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 68: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 69: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Game of the name

~1000s of terms like Actor, birthdate~10s for most sitesCommon across sites

~1b-100b terms like Chuck Norris and Ryan, Oklahama Cannot expect agreement on these Reference by Description Consuming applications reconcile entity references

birthplacetype

citizenOf birthdate

spouseChuck NorrisGena O’Kelley

USA

Ryan, OKActor

March 10, 1940

Page 70: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

What Schema.org data looks like

<h1 itemprop="name"> Chuck Norris</h1> ...

<time datetime="1940-3-10" itemprop="birthDate">

citizenOf birthdate

USA March 10, 1940

Chuck Norris/nm0001569 Actortype

birthplace

birthdatespouse

March 10, 1940Gena O’Kelley

Ryan, OKWikidata

Actortype

Carlos Ray Norris/Q2673

Page 71: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

birthplace

birthDate

spouse

March 10, 1940

citizenOfbirthdate

USA March 10, 1940

birthplacetype

citizenOf birthdate

spouseChuck NorrisGena O’Kelley

USA

Ryan, OKActor

March 10, 1940

Ryan, OKWikidataIMDb

Actortype

Actortype

nm0001569 Q2673

Q8392

Stitch

Page 72: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Aggregate datasets

---

Page 73: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 74: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

DataCommons.org

Page 75: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Page 76: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases
Page 77: Open Knowledge Network - Networking and Information ... · • Existing Entity Stores • Architecture – Catalog – Matching Engine – Facts – Normalization Engine • Use Cases

Thank you