Description:
The URI's in the EIOPA register data are not human readable (e.g. https://rdf.gleif.org/L1/L-097900BEL10000005682-LEI). In the DBO dataset there also exist human readable URI's, which makes generating the language-query pairs more simple. For the translation query, the URI can be used for the translation (not literally, but a URI like sequence is used, which can be easily transformed into a precise URI). This makes for very short generator queries ("select distinct(?a) where { ?a dbo:location [] }"). The generator of LiberAI is restricted to human readable URI (selected by "rdfs:label" property).
Mitigation strategy for now:
Use a complexer query structure including the name property ("gleif-L1:hasLegalName") to then find the correct URI and use it to extract the wanted object.
Further possibilities:
Add human readable URI's, if that is possible
Test whether the translator model is able to work with the abstract URI's
Description: The URI's in the EIOPA register data are not human readable (e.g. https://rdf.gleif.org/L1/L-097900BEL10000005682-LEI). In the DBO dataset there also exist human readable URI's, which makes generating the language-query pairs more simple. For the translation query, the URI can be used for the translation (not literally, but a URI like sequence is used, which can be easily transformed into a precise URI). This makes for very short generator queries ("select distinct(?a) where { ?a dbo:location [] }"). The generator of LiberAI is restricted to human readable URI (selected by "rdfs:label" property).
Mitigation strategy for now: Use a complexer query structure including the name property ("gleif-L1:hasLegalName") to then find the correct URI and use it to extract the wanted object.
Further possibilities: