The QA Systems Table contains links to publications, demo/APIs (if available) and short descriptions of ca. 100 QA systems.
- LC-QuAD 1.0
- LC-QuAD 2.0
- QALD-9
- QALD-8
- QALD-7
- QALD-6
- QALD-5
- QALD-4
- QALD-3
- QALD-2
- QALD-1
- SimpleDBpediaQA
- MLPQ
- KQA Pro
- RuQA 1.0
- RuQA 2.0
- Compositional Wikidata Questions
- TimeQuestions
- CronQuestions
- CLC-QuAD
- SimpleQuestionsWikidata
- Free917
- WebQuestions
- ComplexQuestions
- GraphQuestions
- WebQuestionSP
- ComplexWebQuestions
- 30M Factoid QA
- PathQuestion
- Compositional Freebase Questions
- GrailQA
- TempQuestions
This leaderboard aims to provide a central place to compare the capabilities of different Knowledge Graph Question Answering (KGQA) approaches. It gives a global view of the state-of-the-art (SOTA) across many KGQA benchmarks.
Using a global and open resource, trusting evaluation results will be easier. In particular, we want to close gaps in evaluation campaigns to avoid incomplete or missing comparisons. The ultimate goal is to prevent a replication crisis before it even starts.
If you would like to add a new result, you can just click on the small edit button in the top-right corner of the file for the respective dataset. This allows you to edit the file in Markdown. Simply add a row to the corresponding table in the same format. Make sure that the table stays sorted (with the best result on top). After you've made your change, make sure that the table still looks ok by clicking on the "Preview changes" tab at the top of the page. If everything looks good, go to the bottom of the page, where you see the below form.
Add a name for your proposed change, an optional description, indicate that you would like to "Create a new branch for this commit and start a pull request", and click on "Propose file change".
For adding a new dataset or task, you can also follow the steps above. Alternatively, you can fork the repository. In both cases, follow the steps below:
- If your dataset is completely new, create a new file and link to it in the table of contents above.
- Briefly describe the dataset and include relevant references.
- Describe the evaluation setting and evaluation metric.
- Show how an annotated example of the dataset looks like.
- Add a download link if available.
- Copy the below table and fill in at least two results (including the state-of-the-art) for your dataset (change Metric1/Metric2/Metric3 to the metric of your dataset).
- Submit your change as a pull request.
Model / System | Year | Metric1 | Metric2 | Metric3 | Reported by |
---|---|---|---|---|---|
Instructions for building the website locally using Jekyll can be found here.
This site is based on https://nlpprogress.com/ and thus, a great thanks goes to Sebastian Ruder.