A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and...

25
A Review of Relational Machine Learning for Knowledge Graphs Maximilian Nickel, Kevin Murphy, Volker Tresp, and Evgeniy Gabrilovich (arXiv:1503.00759v1) Discussion by: Piyush Rai June 12, 2015 Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 1

Transcript of A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and...

Page 1: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

A Review of Relational Machine Learning for

Knowledge Graphs

Maximilian Nickel, Kevin Murphy,Volker Tresp, and Evgeniy Gabrilovich

(arXiv:1503.00759v1)

Discussion by: Piyush Rai

June 12, 2015

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 1

Page 2: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Learning from Relational Data

Non-Relational data: objects as features

(Multi)-Relational data: objects as their relationship(s) to other objects

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 2

Page 3: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Outline

Introduction to Knowledge Graphs

Knowledge RepresentationOpen vs Closed World AssumptionKnowledge Base ConstructionUses of Knowledge GraphsTypical Learning Tasks on Knowledge Graphs

Statistical Relational Learning on Knowledge Graphs

Problem Formulation and Training Data GenerationPenalized Maximum Likelihood TrainingPairwise Loss TrainingLatent Feature Models and Graph Feature Models

Latent Feature Models

Current and Future Directions

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 3

Page 4: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Knowledge Graph Representation

Figure: Nodes: Entities; Edges: Relations

Can be extracted from unstructured/semi-structured data and stored usingtriplets of the form subject-predicate-object or entity-relation-entity

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 4

Page 5: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Open vs Closed World Assumption

Figure: Nodes: Entities; Edges: Relations

Closed world assumption (CWA): Non-existing triplet = false relationship

Open world assumption (OWA): Non-existing triplet = unknown relationship

More appropriate as knowledge graphs are highly incomplete

Local-closed world assumption (LCWA)

Once we have observed (ei , rk , ej), any non-existing (ei , rk , .) is indeed falseAppropriate for functional relations (e.g., bornIn)

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 5

Page 6: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Knowledge Graph / Knowledge Base Construction

Curated approaches

Triplets are created manually by a closed group of expertsData is reliable; algorithms can easily get high accuracies

Collaborative approaches

Triplets are created manually by an open group of volunteersData is reliable but incomplete; algorithms can easily get high accuracies

Automatic Knowledge Base Construction (AKBC)

Automated semi-structured approaches: Triplets extracted automatically fromsemi-structured text such as infoboxes in Wikipedia, via hand-crafted rules,learned rules, regular expressions, etc.

Automated unstructured approaches: Triplets extracted automatically fromunstructured text via Machine Learning and NLP techniques

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 6

Page 7: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Some Real-World Knowledge Bases

Schema-based: Entities and relations have unique identifiers

Schema-free: Multiple entities/relations could refer to the same semantics(e.g, bornIn and placeOfBirth, both may be present in the knowledge base)

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 7

Page 8: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

What might Knowledge Bases be useful for?

Improved search results (Google’s Knowledge Graph; Microsoft’s Satori)

Question Answering systems (e.g., IBM’s Watson)

Decision support systems in healthcare (e.g., LinkedLifeData)

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 8

Page 9: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Machine Learning with/for Knowledge Bases

Feature learning (i.e., embeddings) for entities and relations

Link-Prediction

Discovering new facts from existing facts in the knowledge baseCorrecting wrong facts (e.g., Obama was born in Kenya) using reliable/correctfacts (e.g., Obama is president of USA) in the knowledge base

Entity/Relation Resolution

Obama, Barack Obama, 44th US President, all refer to the same personBorn-in, place-of-birth, both refer to the same relation

Entity/Relation Clustering

Entity/Relation Ranking. E.g.,

Given an entity e1 and relation (r), give a ranked list of entities e2 on theother side of the relation (e1 − r − ?)Given a pair of entities (e1, e2), predict the most-likely relations (e1 − ?− e2)

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 9

Page 10: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Statistical Modeling of Knowledge Graphs

Given: knowledge graph/knowledge base, consisting of Ne entities, Nr

relations, and facts (triplets: entity1-relation-entity2)

Set of entities E = {e1, . . . , eNe}, set of relational R = {r1, . . . , rNr

}

Each possible triplet xijk = (ei , rk , ej), with yijk = {0, 1} denoting itsexistence/validity

Can store all possible triplets using a binary tensor Y ∈ {0, 1}Ne×Ne×Nr

Interpretation of yijk = 0 depends on open/closed/local-closed worldassumption. Number of 1s is usually very small in either case.

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 10

Page 11: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

How to get negative examples?

Most knowledge graphs contain only positive examples (no false facts)

Thus, positive examples (yijk = 1) are naturally given to us

Denote positive examples (ei , rk , ej), s.t. yijk = 1, by the set D+

How to generate the set D− of negative examples (i.e., for which yijk = 0)?

One way is to assume everything not in D+ to be negative (subject to the

constraints on the entity/relation type). Such D− can be very massive.

Another way is to generate D− as

Caveat: Still no guarantee that each entry in D− is necessarily negative

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 11

Page 12: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Statistical Modeling of Knowledge Graphs

The random variables yijk ∈ {0, 1} in Y are correlated with each other

Three main ways to model the correlations

M1: yijk ’s are iid given the latent features of entities and relations (latentfeature models)

M2: yijk ’s are iid given observed graph features and additional parameters(graph feature models)

M3: yijk ’s have local interactions (Markov Random Fields)

M1 and M2 predict the existence of yijk via a score function f (xijk ; Θ)

Here is a typical probabilistic approach to parameter learning in M1 and M2

Training via (penalized) maximum likelihood, or fully Bayesian inference

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 12

Page 13: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Pairwise Loss based Training

If we can’t trust negatives to be really negative, have the model score themlower than the positives

Note: f can be a function or a probability model.

Optimization-based, penalized ML, or Bayesian, any approach can be usedfor parameter estimation

Online methods preferred (sample one positive and one nagative example ineach round..)

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 13

Page 14: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Statistical Modeling of Knowledge Graphs

Two main approaches

Latent feature models

Assume each entity ei to have an embedding ei ∈ RHe

Assume each relation type rk to be parameterized by some Wk

Define score of a triplet (ei , rk , ej) as some function f (ei , ej ,Wk), e.g.,

f (ei , ej ,Wk) = e⊤i Wkej where Wk ∈ RHe×He

f (ei , ej ,Wk) = −dist(ei +Wk , ej) where Wk ∈ RHe

Score can be turned into a probability if needed (e.g., via a logistic function)Assumptions can be imposed on ei ’s and Wk ’s (e.g., sparsity, non-negativity)

Graph feature models

Score of a triplet (ei , rk , ej) depends on graph-based notions (e.g., number ofall paths of some length L or less, number of common neighbors).Some commonly used methods: Katz index, Adamic-Adar index, PageRanking algorithm

Latent feature models and graph feature models can also be combined (somerecent work; see reference [103] in the survey paper)

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 14

Page 15: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

More on Latent Feature Models

Assume the Ne × Nh matrix E = [e1; . . . ; eN ] contains the latent features(i.e., embeddings) of the Ne entities. E is shared across all relations

A bilinear latent feature model for relation rk (parameterized by Nh × Nh

matrix Wk) models the score as: Yk ≈ EWkE⊤

yijk ≈ e⊤i Wkej = w⊤

k (ei ⊗ ej) where wk = vec(Wk)

Basically, a linear model

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 15

Page 16: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Nonlinear Latent Feature Models

Replace the linear mapping fijk = w⊤

k (ei ⊗ ej) by a nonlinear one

fijk = w⊤

k g(ha) (where g is some nonlinear function)

ha = A⊤

k φij

φij = [ei ; ej ]

Another model:

fijk = w⊤g(hc) (where g is some nonlinear function)

hc = C⊤φijk

φijk = [ei ; ej ; rk ]

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 16

Page 17: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Architecture of Google Knowledge Vault

A hybrid, fusion-based architecture consisting of latent feature model, graphfeature model, and an information extraction component

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 17

Page 18: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Extensions and Future Work

Incorporating type constraints (e.g., relation “married-to” can only involveentities that correspond to “people”) or functional constraints (e.g., a personcan be born in only one city).

Generalizing to new entities and new relations

Incorporating other sources (e.g., text) in addition to knowledge base data

Including other dimensions such as time (e.g., Larry Page was Google CEOfrom 2001-2011)

Models that support complex queries on probabilistic knowledge graphs, e.g.,

“Find the athlete who is from Romania who won gold in 3000m and bronze in1500m in 1984 Olympics”

Richer model structures (e.g., hierarchies/clusters among relations/entities)

Scaling up to web-scale knowledge bases (also making the model depend onlyon the known facts, i.e., the 1s, in the data)

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 18

Page 19: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Extensions and Future Work

Incorporating type constraints (e.g., relation “married-to” can only involveentities that correspond to “people”) or functional constraints (e.g., a personcan be born in only one city).

Generalizing to new entities and new relations

Incorporating other sources (e.g., text) in addition to knowledge base data

Including other dimensions such as time (e.g., Larry Page was Google CEOfrom 2001-2011)

Models that support complex queries on probabilistic knowledge graphs, e.g.,

“Find the athlete who is from Romania who won gold in 3000m and bronze in1500m in 1984 Olympics”

Richer model structures (e.g., hierarchies/clusters among relations/entities)

Scaling up to web-scale knowledge bases (also making the model depend onlyon the known facts, i.e., the 1s, in the data)

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 18

Page 20: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Extensions and Future Work

Incorporating type constraints (e.g., relation “married-to” can only involveentities that correspond to “people”) or functional constraints (e.g., a personcan be born in only one city).

Generalizing to new entities and new relations

Incorporating other sources (e.g., text) in addition to knowledge base data

Including other dimensions such as time (e.g., Larry Page was Google CEOfrom 2001-2011)

Models that support complex queries on probabilistic knowledge graphs, e.g.,

“Find the athlete who is from Romania who won gold in 3000m and bronze in1500m in 1984 Olympics”

Richer model structures (e.g., hierarchies/clusters among relations/entities)

Scaling up to web-scale knowledge bases (also making the model depend onlyon the known facts, i.e., the 1s, in the data)

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 18

Page 21: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Extensions and Future Work

Incorporating type constraints (e.g., relation “married-to” can only involveentities that correspond to “people”) or functional constraints (e.g., a personcan be born in only one city).

Generalizing to new entities and new relations

Incorporating other sources (e.g., text) in addition to knowledge base data

Including other dimensions such as time (e.g., Larry Page was Google CEOfrom 2001-2011)

Models that support complex queries on probabilistic knowledge graphs, e.g.,

“Find the athlete who is from Romania who won gold in 3000m and bronze in1500m in 1984 Olympics”

Richer model structures (e.g., hierarchies/clusters among relations/entities)

Scaling up to web-scale knowledge bases (also making the model depend onlyon the known facts, i.e., the 1s, in the data)

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 18

Page 22: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Extensions and Future Work

Incorporating type constraints (e.g., relation “married-to” can only involveentities that correspond to “people”) or functional constraints (e.g., a personcan be born in only one city).

Generalizing to new entities and new relations

Incorporating other sources (e.g., text) in addition to knowledge base data

Including other dimensions such as time (e.g., Larry Page was Google CEOfrom 2001-2011)

Models that support complex queries on probabilistic knowledge graphs, e.g.,

“Find the athlete who is from Romania who won gold in 3000m and bronze in1500m in 1984 Olympics”

Richer model structures (e.g., hierarchies/clusters among relations/entities)

Scaling up to web-scale knowledge bases (also making the model depend onlyon the known facts, i.e., the 1s, in the data)

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 18

Page 23: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Extensions and Future Work

Incorporating type constraints (e.g., relation “married-to” can only involveentities that correspond to “people”) or functional constraints (e.g., a personcan be born in only one city).

Generalizing to new entities and new relations

Incorporating other sources (e.g., text) in addition to knowledge base data

Including other dimensions such as time (e.g., Larry Page was Google CEOfrom 2001-2011)

Models that support complex queries on probabilistic knowledge graphs, e.g.,

“Find the athlete who is from Romania who won gold in 3000m and bronze in1500m in 1984 Olympics”

Richer model structures (e.g., hierarchies/clusters among relations/entities)

Scaling up to web-scale knowledge bases (also making the model depend onlyon the known facts, i.e., the 1s, in the data)

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 18

Page 24: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Extensions and Future Work

Incorporating type constraints (e.g., relation “married-to” can only involveentities that correspond to “people”) or functional constraints (e.g., a personcan be born in only one city).

Generalizing to new entities and new relations

Incorporating other sources (e.g., text) in addition to knowledge base data

Including other dimensions such as time (e.g., Larry Page was Google CEOfrom 2001-2011)

Models that support complex queries on probabilistic knowledge graphs, e.g.,

“Find the athlete who is from Romania who won gold in 3000m and bronze in1500m in 1984 Olympics”

Richer model structures (e.g., hierarchies/clusters among relations/entities)

Scaling up to web-scale knowledge bases (also making the model depend onlyon the known facts, i.e., the 1s, in the data)

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 18

Page 25: A Review of Relational Machine Learning for Knowledge Graphs · Schema-based: Entities and relations have unique identifiers Schema-free: Multiple entities/relations could refer

Thanks! Questions?

Nickel et al. (arXiv:1503.00759v1) A Review of Relational Machine Learning for Knowledge Graphs 19