Open KonradHoeffner opened 2 years ago
It seems that the entity-linking service does not return any results. Note that for entity-linking to work, Elasticsearch should be running and have required indexes created from the knowledge base (e.g., DBpedia). Please verify if Elasticsearch service is running and has the necessary indexes.
Alternatively, you can try the instructions on this branch: https://github.com/dice-group/TeBaQA/tree/speaker-integration
This has installation scripts for windows which will install and start the necessary services. It also has a frontend interface where you can upload your data, so you don't have to do indexing manually.
The problem occurs in the demo and the docker version as well, shouldn't it be running there?
Fixed by restarting the demo. If you want to run locally you have to install elasticsearch and install the indices first.
We tried that but it didn't work, it seemed like it only works with a specific ElasticSearch version. It would really help if you included Elasticsearch in the Dockerfile so we could have a reproducible setup.
elasticsearch version is 6.6.1. I'm not so sure if I want to add the indexing step to the docker file, since it takes quite long to generate the indices. I consider that for the future. For now, I added the elasticsearch version in the readme
It would be extremely helpful because the big benefit of docker is that someone else can use a piece of software as it is without needing to worry about a setup process. However if a required part is not included then this does not work. It could also be a second docker file so that there is one without and one with the index.
Using any of the 8 example questions results in "no answers were found". This applies to the online demo, docker containers built from the master branch, commit c879b1509f762af1142f8189d00312305be24e21, and to the build and run scripts as well. Version 1.1 was tested as well with the same result.
Log