Conference item
Most probable explanations for probabilistic database queries
- Abstract:
- Forming the foundations of large-scale knowledge bases, probabilistic databases have been widely studied in the literature. In particular, probabilistic query evaluation has been investigated intensively as a central inference mechanism. However, despite its power, query evaluation alone cannot extract all the relevant information encompassed in large-scale knowledge bases. To exploit this potential, we study two inference tasks; namely finding the most probable database and the most probable hypothesis for a given query. As natural counterparts of most probable explanations (MPE) and maximum a posteriori hypotheses (MAP) in probabilistic graphical models, they can be used in a variety of applications that involve prediction or diagnosis tasks. We investigate these problems relative to a variety of query languages, ranging from conjunctive queries to ontology-mediated queries, and provide a detailed complexity analysis.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Accepted manuscript, pdf, 313.9KB, Terms of use)
-
- Publisher copy:
- 10.24963/ijcai.2017/132
- Publisher:
- IJCAI
- Host title:
- 26th International Joint Conference on Artificial Intelligence (IJCAI 2017), Melbourne, Australia, 19-25 August 2017
- Journal:
- 26th International Joint Conference on Artificial Intelligence (IJCAI 2017) More from this journal
- Publication date:
- 2017-08-19
- Acceptance date:
- 2017-04-24
- Event location:
- Melbourne‚ Australia
- DOI:
- Pubs id:
-
pubs:701735
- UUID:
-
uuid:91cc7bb1-633e-4310-9155-5f28d78f9881
- Local pid:
-
pubs:701735
- Source identifiers:
-
701735
- Deposit date:
-
2017-06-22
Terms of use
- Copyright holder:
- © 2017, IJCAI
- Copyright date:
- 2017
- Notes:
- This paper has been accepted for the 26th International Joint Conference on Artificial Intelligence (IJCAI-17), Melbourne, Australia, 19-25 August 2017
If you are the owner of this record, you can report an update to it here: Report update to this record