Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

offset duplicated #41

Open
agilll opened this issue Apr 25, 2019 · 1 comment
Open

offset duplicated #41

agilll opened this issue Apr 25, 2019 · 1 comment

Comments

@agilll
Copy link

agilll commented Apr 25, 2019

Hi everybody:

I have tried the following text in the DBpedia SpotLight demo.

"Artaxerxes III was succeeded by Artaxerxes IV Arses”

I get the following strange result.

"Artaxerxes III was succeeded by Artaxerxes IV ArsesArtaxerxes IV ArsesArtaxerxes IV Arses, who before he could act was also poisoned"

If I make an API call, I get two different entities identified in the same offset 32:

@URI-> http://dbpedia.org/resource/Arses_of_Persia
@surfaceForm-> Artaxerxes IV Arses
@offset-> 32

and

@URI-> http://dbpedia.org/resource/Artaxerxes_III
@surfaceForm-> Artaxerxes
@offset-> 32

May be this is a bug? or is there an explanation I don't get?

@fanavarro
Copy link

fanavarro commented Jul 28, 2020

Same here, I am using the input
host, BBC Wildlife Specials
and then I have the result
host, BBC Wildlife SpecialsBBC Wildlife SpecialsBBC Wildlife Specials

This includes the following entities:

However, I would like to obtain the longest match only, which should be BBC Wildlife Specials. If this possible?

This happens in the demo page as well as in the API used through the docker container.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants