You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DBpedia Spotlight returns not only URIs for entities but also entity types. In get_dbpedia_uris() these values are currently omitted from the output. If kept, these entity types could be used to classify entities without additional SPARQL queries, for example if the textual data does not contain pre-annotated named entities.
The text was updated successfully, but these errors were encountered:
This will be absolutely useful, to keep the number of arguments minimal: I do not think, we need the additional argument. We should return types by default, and leave it to users to delete the column, if it is not wanted.
However, what we should do: document the columns of the return value, so that we know what we get.
We now have a list 'types' in the output table, which is a list with the parsed result. Potentially, this is not yet the ideal data representation, but I would leave the further discussion to: #27
DBpedia Spotlight returns not only URIs for entities but also entity types. In
get_dbpedia_uris()
these values are currently omitted from the output. If kept, these entity types could be used to classify entities without additional SPARQL queries, for example if the textual data does not contain pre-annotated named entities.The text was updated successfully, but these errors were encountered: