LASLAfiles_Latin_APNformat

Open data API in a single place

Provided by Université de Liège

Get early access to LASLAfiles_Latin_APNformat API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Université de Liège catalog

Country of origin

Belgium

Updated

2023.09.29 08:16

Created

2023.09.29

Available languages

English

Keywords

NLP, Classical Latin, Linguistic annotation, LASLA

Datasource

Official portal for European data link

Quality scoring

Dataset description

We recommend to access the Dataverse using the "Tree View". The folder 'LASLA Files APN format' contains the LASLA Latin Files in a APN format as described in the documentation found in the subfolder 'APN_Files_Documentation'. The subfolder 'APN_Files_Total' contains all the APN files of the LASLA corpus. The Subfolder 'APN_Files_for_Hyperbase' contains the files that are used to create the datasets that can be searched on HyperbaseWeb (http://hyperbase.unice.fr/hyperbase/). The LASLA files have been converted to the CoNLL-U format and enriched with the links to the LiLa Knowledge Base by the LiLa team: the files are available on Zenodo (https://doi.org/10.5281/zenodo.5961377) and Github (https://github.com/CIRCSE/LASLA). The files in this repository are shared under the license CC BY-NC-SA 4.0.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service