Mappings to FrameBase
This page contains the downloadable versions of the mappings from PropBank (PB), NomBank (NB) and FrameNet (FN) predicates and arguments to FrameBase classes and roles, both in TSV and RDF formats. These mappings are used by PIKES for extracting knowledge according to the FrameBase ontological schema.
Mappings from FrameNet to FrameBase were generated straightforwardly exploiting the fact that FrameBase is derived from FrameNet; mappings from PropBank / NomBank to FrameBase were generated leveraging both existing manually-crafted mappings in SemLink and OntoNotes frame files and by learning mappings from automatically annotated data (the details of the process are described in a paper under review).
Predicate mappings
Each mapping relates a (PB/NB/FN predicate, lemma, POS-tag) triple to a FrameBase microframe class. Equivalent (as of owl:equivalentClass) microframe classes have been merged with only a representative class for each cluster being used as target for the mappings. Predicate mappings are provided in two formats:
- TSV predicate mappings, using four columns for: PB/NB/FN predicate ID, lemma, POS, FrameBase class URI.
- RDF Turtle predicate mappings, where each mapping is a reified relation identified by a URI and described by properties ks:predicate, ks:lemma, ks:pos, and ks:class (ks prefix for http://dkm.fbk.eu/ontologies/knowledgestore#).
Argument mappings
Each mapping associates a predicate argument to a FrameBase property URI (predicate arguments are frame elements for FrameNet, and predicate / role pairs for PropBank and NomBank). Argument mappings are provided in two formats:
- TSV argument mappings, using two columns: predicate @ role, and FrameBase property URI.
- RDF Turtle argument mappings, where each mapping is a reified relation identified by a URI and described by properties ks:role (pointing to the URI for the predicate argument as defined in PreMOn), and ks:property.
