1 / 34

Believe It or Not – Adding belief annotations to databases

This paper discusses the concept of belief databases, which manage data and curation based on modal and default logic, and their implementation on top of the relational model.

aengland
Télécharger la présentation

Believe It or Not – Adding belief annotations to databases

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. August 25, VLDB 2009 Believe It or Not – Adding belief annotations to databases Wolfgang Gatterbauer, Magda Balazinska, Nodira Khoussainova, and Dan Suciu • University of Washingtonhttp://db.cs.washington.edu/beliefDB/

  2. High-level overview • DBMS: manage consistent data • Applications need inconsistent DM • Scientific databases • Internet community databases • Community DBMS: manage inconsistent views • This work: Belief databases • manage data and curation • grounded in modal and default logic • implemented on top of relational model reason: disagreement !

  3. Agenda • Motivating example • Logic foundations • Relational implementation • Discussion

  4. Motivating application • NatureMapping project (http://depts.washington.edu/natmap/) • volunter contribute animal observations • one person curates the database problem: does not scale!

  5. 1. Distinct database instances Alice Bob D1: Belief worlds: individually consistent, mutually possibly inconsistent

  6. 1. Distinct database instances Alice Bob Q: Who believes something different than Alice and what? BeliefSQL I: Alice believes that she saw a crow. select U2.name, S1.species, S2.species from Users as U, BELIEF ‘Alice’ Sightings as S1, BELIEF U.uid Sightings as S2, where S1.sid = S2.sid and S1.species <> S2.species insert into BELIEF ‘Alice’Sightings values (‘s2’,‘Alice’,‘Crow’,’06-14-08’,‘Lake Placid’) I: Bob believes that she actually saw a raven. insert into BELIEF ‘Bob’ Sightings values (‘s2’,‘Alice’,‘Raven’,’06-14-08’,‘Lake Placid’) A: {(‘Bob’, ‘Crow’, ‘Raven’)}

  7. 2. Open world assumption Alice Bob − Carol − Adapted key constraints ! D2: Model incomplete knowledge with exlicit negative beliefs

  8. 2. Open world assumption I: Carol does not believe that Alice saw a crow nor a raven. insert into BELIEF ‘Carol’ notSightings values (‘s2’,‘Alice’,‘Crow’,’06-14-08’,‘Lake Placid’) insert into BELIEF ‘Carol’ notSightings values (‘s2’,‘Alice’,‘Raven’,’06-14-08’,‘Lake Placid’) Alice Bob − Carol −

  9. 2. Open world assumption Q: Who disagrees with a sighting from ‘06-14-08’ that Alice believes? select U.name, S1.species from Users as U, BELIEF ‘Alice’ Sightings as S1, BELIEF U.uid not Sightings as S2 where S1.sid = S2.sid and S1.uid = S2.uid and S1.species = S2.species and S1.date = ‘06-14-08’ and S2.date = ‘06-14-08’ and S1.location = S2.location Alice Bob A: {(‘Bob’, ‘Crow’), (‘Carol’, ‘Crow’)} − Carol −

  10. 3. Higher-order beliefs Alice Bob Alice Bob D3: Beliefs about other user’s beliefs: allow discussion between users

  11. 3. Higher-order beliefs I: According to Bob, Alice believes that the feathers of the sighted animal were plain black. insert into BELIEF ‘Bob’ BELIEF ‘Alice’ Comments values (‘c1’, ‘plain black feathers’, ‘s2’) Alice Bob Alice Bob

  12. 3. Higher-order beliefs Q: Which comments does Alice believe according to Bob, which he does not believe himself? select C1.cid, C1.comment from BELIEF ‘Bob’ BELIEF ‘Alice’ Comments as C1, BELIEF ‘Bob’ not Comments as C2 where C1.cid = C2.cid and C1.comment = C2.comment and C1.sid = C2.sid Alice Bob A: {(‘c1’,‘plain-black feathers’)} Alice Bob

  13. 3. Higher-order beliefs Q: Which comments does Alice believe according to somebody, which (s)he does not believe themself? select U.name, C1.sid, C1.comment from Users as U, BELIEF U.uid BELIEF ‘Alice’ Comments as C1, BELIEF U.uid not Comments as C2 where C1.cid = C2.cid and C1.comment = C2.comment and C1.sid = C2.sid Alice Bob A: {(‘Bob’, ‘c1’, ‘plain-black feathers’)} Alice Bob

  14. 4. Message board assumption Alice Bob Alice Bob D4: Default assumption: models a trusting attitude & avoids repeated inserts

  15. 4. Message board assumption Q: Which animal sightings does Alice believe according to Bob, which he does not believe himself? Alice select S1.sid, S1.species from BELIEF ‘Bob’ BELIEF ‘Alice’ Sightings as S1, BELIEF ‘Bob’ not Sightings as S2 where S1.sid = S2.sid and S1.uid = S2.uid and S1.species = S2.species and S1.date = S2.date and S1.location = S2.location Bob A: {(‘s2’, ‘Crow’)} Alice Bob

  16. What we have seen so far • 4 Design decisions for Belief Database model • Distinct belief worlds • Open world assumption (OWA) • Higher-order beliefs • Message board assumption • BeliefSQL • SQL + ‘BELIEF’ (+ ‘not’)

  17. Agenda • Motivating example • Logic foundations • Relational implementation • Discussion

  18. Logic foundations: Belief statements … Bob Alice insert into BELIEF ‘Alice’ S values (‘s2’, ‘Alice’, ‘Crow’,…) Carol Alice … i: ☐Alice S+(‘s2’,‘Alice’,‘Crow’,…) Alice … modal operator& belief path (w) relational tuple (t) Alice BobAlice sign (s) Bob Carol ε … belief statement “annotation of ground tuple”  = ☐w ts Carol … Alice Belief database D = {1, …, n} Bob …

  19. Logic foundations: Entailment … Bob Alice Carol Alice … Bob Alice Alice select * from BELIEF ‘Bob’ BELIEF ‘Alice’ S … Alice BobAlice Bob Carol ε One belief annotation: … D = {1} Carol 1=☐Alice S+(…‘Crow’,…) … Alice D ☐BobAlice S+(…‘Crow’,…) More than one entailed belief: Bob …

  20. Logic foundations: Message board assumption Message board assumption Default logic  : ☐u and ☐uwts consistent with D ☐u non-monotonic reasoning ! D Explicit beliefs (annotations) D \ D Implicit beliefs (assumptions) D Entailed beliefs (extension) If D ☐wts then D ☐uwts belief database “contains” more than the explicit belief annotations !

  21. “Semi-formal” problem statement INPUT OUTPUT Belief statements i1: 1 i2: 2 ... in: n q(x) :−☐wRi+(xi) Adaptedkey constraints Message board assumption Belief Conjunctive Queries (BCQ)  : ☐u q(x) :− ☐w1R1s1(x1), …, ☐wgRgsg(xg) ☐u D  ? D ☐w1…wdR+(x1,…xl) ?

  22. Agenda • Motivating example • Logic foundations • Relational implementation • Discussion

  23. Canonical Kripke structure Belief statements* i1: s11+ i2: ☐Bob s11− i3: ☐Bob s12− i4: ☐Alice s21+ i5: ☐Alice c11+ i6: ☐Bob s22+ i7: ☐BobAlice c21+ i8: ☐Bob c22+ Carol #1 Alice Carol {s11+,s21+,c11+} Carol #0 Bob #3 Alice Carol {s11+} {s11+,s21+,c11+,c21+} Bob Bob #2 {s11−,s12−,s22+,c22+} Message board assumption  : ☐i ☐i * Running example from the paper

  24. Relational representation

  25. Example Translation of a Belief CQ (BCQ) Q: Who disagrees with a sighting from ’06-14-08’ that Alice believes? BeliefSQL Translation into SQL select U.name, S1.species from Users as U, BELIEF ‘Alice’ Sightings as S1, BELIEF U.uid not Sightings as S2 where S1.sid = S2.sid and S1.uid = S2.uid and S1.species = S2.species and S1.date = ‘06-14-08’ and S2.date = ‘06-14-08’ and S1.location = S2.location select E1.uid as uid1, V.tid, V.sid, R.uid, R.species, R.date, R.location, V.s into T2 from E as E1, Sightings_V as V, Sightings_STAR as R where E1.wid1=0 and V.wid=E1.wid2 and V.tid=R.tid and E1.uid='1'; select E1.uid as uid1, V.tid, V.sid, R.uid, R.species, R.date, R.location, V.s into T1 from E as E1, Sightings_V as V, Sightings_STAR as R where E1.wid1=0 and V.wid=E1.wid2 and V.tid=R.tid; select T1.uid1, T2.species from T1 as T1, T2 as T2 where T1.sid=T2.sid and ((T1.s=0 and T1.uid=T2.uid and T1.species=T2.species and T1.date='6-14-08' and T1.location=T2.location) or (T1.s=1 and (T1.uid<>T2.uid or T1.species<>T2.species or T1.date<>'6-14-08' or T1.location<>T2.location))) and T2.s=1 and T2.date='6-14-08'; drop table T2; drop table T1; q(x,y) :− ☐Alice S+(u,v,y,‘06-14-08’,z), ☐x S−(u,v,y,‘06-14-08’,z)

  26. Agenda • Motivating example • Logic foundations • Relational implementation • Discussion

  27. Experiments Size |R*| m … #users Relative overhead ρ := ρ = O(mdmax) n dmax … maximum depth of belief annotation In theory: e.g. 100 users, max. depth 2 ρ 10,000 ρ 21 – 1,009 Experiments: Size not limitation of semantics, but of relational implementation! Time Depends on type of query (3 types in paper) Q1: ~0.1 s Q2: ~0.4 s Q3: ~4.5 s Experiments on 10,000 annotations (ρ =22.4): Considerable speed-up to come!

  28. Inspirations and related work (excerpt) • Annotations • Buneman et al. [ICDT 2001 / ICDT 2007] • Bhagwat et al. [VLDBJ 2005], Geerts et al. [ICDE 2006] • Srivastava & Velegrakis [SIGMOD 2007] • Modal logic • Fagin et al. [1995] • Calvanese et al. [IS 2008] • Nguyen [LJ-IGPL 2008] • Uncertain / incomplete information • Sarma et al. [ICDE 2006] • Green & Tannen [IEEE Data Eng. 2006] • Dalvi & Suciu [PODS 2007] • Inconsistency / key violations • Arenas et al. [PODS 1999] • Fuxman et al. [SIGMOD 2005] • Peer-to-peer computing / collaborative data sharing • Bernstein et al. [WebDB 2002] • Ives et al. [SIGMOD record 2008]

  29. Conclusions • Proposed BELIEF databases • Goal: manage, curate inconsistent data • Implementation • Logical foundations • Relational translation • Current work • making it compact and fast

  30. BACKUP

  31. Relative overhead of relational representation Distribution of belief path depths (Pr[k=x])

  32. Query types and execution times

  33. Belief Conjunctive Queries (BCQ)

  34. Revisiting the semantics / the user (3) ? BELIEF ’Alice’ (…,’eagle’,…) -> ’Alice’ASSERTS (…,’eagle’,…) -> Structured discourse (2) BeliefSQL BELIEF ’Bob’ BELIEF ’Alice’ (…,’black feathers’,…) Conflicts in belief worlds: OWA, keys, ML, DA -> ’Bob’SUGGESTS that the ASSUMPTION (…,’black feathers’,…) has led ‘Alice’ to her original observation (1) SQL Standard relational model

More Related