DISSICON: DISSINET lexico-semantic network of concepts and actions

Open data API in a single place

Provided by Zenodo

Get early access to DISSICON: DISSINET lexico-semantic network of concepts and actions API!

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

Dataset information

Country of origin
Updated
2026.01.21 00:00
Created
2025.01.01
Available languages
English
Keywords
Latin, historical trials, inquisition, lexico-semantic network, inquisition records, trial records, WordNet
Quality scoring

Dataset description

This is a JSON-format, machine-operable, open-licence lexicographic resource, which forms a subset of the research database of the “Dissident Networks Project” (DISSINET, https://dissinet.cz). It focuses on conceptual and verbal entities which hold the database semantically together - its lexico-semantic network. DISSICON stands for DISSI(NET) and CON(CEPTUAL NETWORK). The broader project focuses on the semantic annotation and computational analysis of medieval inquisition records in a social science framework, which for the most part defines (albeit not exclusively) the focus of this lexico-semantic network. The version published here contains the full set of: Action entities (n=945), that is verbs and multiword verbal expressions (entities.json); Concept entities (n=6,131), that is non-verbal parts of speech (nouns, adjectives, adverbs, occasionally others), including multiword expressions (entities.json); semantic relations (n=10,171) between those entities (relations.json), including hypernymy (n=5,584), actant role semantics / functors (n=2,045), synonymy (n=518), action/event equivalence (n=795), and others; those Reference entities that Concepts and Actions use for pointing to external resources, typically to WordNet and the Lila Lemma Collection (entities.json); Value entities mostly denoting textual values of IDs within the resources denoted in those References (entities.json). The dataset’s value for social science history and data-oriented history is that it provides an in-progress, but already powerful machine-operable ontology born from research into medieval inquisition records, including sometimes quite elaborated hypernym paths as well as other semantic relations (synonymy, meaning of all actant slots under specific verbs, etc.). The value of DISSICON for lexicography is that it maps various uses of verbs and other parts of speech, with special attention paid to meanings of Latin verbs and concepts encountered in medieval inquisition records and their semantic anchoring in a network of English-language analytical concepts. In addition, verbs have an extensively described valency in terms of (1) the entity type a given actant slot can accept (Person, Group, Physical Object, Concept...), (2) morphosyntactic connectivity (case and preposition), and (3) a highly granular rendering of functors, i.e. roles held by an entity when it occupies a given actant slot (e.g., actant slots for giver, beneficiary, and gift under the Latin verb "dedit" / "do", in the meaning of "to give as gift"). A significant part of the entities refers to WordNet for meaning identifiers, but we create our own meanings whenever WordNet did not yield a meaning with a satisfactory definition. DISSICON thus provides a referenceable resource for meanings not covered by Latin WordNet (or even WordNet at large). The dataset identities are UUID-based, and our internal processes make the meanings highly persistent. The typical users of this dataset will be users of a new instance of the InkVisitor software, who will decide to pre-populate their instance with this existing data, if they find it useful. (V1 was used to populate the MedHate instance of InkVisitor.) A basic, gradually extended documentation of the broader data model is available from the website From texts to structured data: Building knowledge graphs through Computer-Assisted Semantic Text Modelling (CASTEMO). A brief introduction in the data collection approach are available at InkVisitor | CASTEMO. DISSICON contains the full set of Actions and Concepts, and as such, it is not so reliable and thorough as the more curated subset called DISSILEX, which focuses on the description of Latin verbs. The work is ongoing and the semantic relations may be of imbalanced depth, can contain inconsistencies, and the mapping of this ontology upon some relevant standards, such as Ontolex Lemon, is still due. We hope to make some progress on this soon.  The contributions to the up-to-date version of the DISSICON dataset (as per the Audits feature of the InkVisitor software, in one of whose instances the database is curated) are as follows, with contributions 5% or more amounting to authorship, and 1% or more but less than 5% to contributorship: David Zbíral 39.64 %; Robert Shaw 19.01 %; Katia Riccardo 18.08 %; Katalin Suba 14.21 %; Davor Salihović 5.34 %; Stanisław Banach 1.91 %. The creation of the dataset has received funding from the European Research Council (ERC) under the European Union’s Horizon 2020 research and innovation programme (grant agreement No. 101000442, project “Networks of Dissent: Computational Modelling of Dissident and Inquisitorial Cultures in Medieval Europe”).
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
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.

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

Copyright © 2026. Made by Apitalks