IRI:
https://w3id.org/framester/framenet/tbox/
Current version:
1.0 added GenericFrameElement class for generalizing over potentially similar frame elements (handle with care: the assumption in FrameNet is that frame elements homonymy does not ensure semantic similarity) 0.9 revised labels and some restrictions 0.8 created after manual revision of autamatically generated schema with Semion rules
Authors:
Aldo Gangemi and Andrea Nuzzolese with Semion rules and manual revision
Other visualisation:
Ontology source

Abstract

Inheritance Not surprisingly, Inheritance, as our most formally defined relation, is an exact match for an ontologically defined relation, namely subtyping or “is-a”, as mentioned above. Because these relations are so well-defined formally, there is very little else that needs to be said about Inheritance here. As discussed above, the Inheritance relation implies the correspondence of the Parent frame and its FEs to the Child frame and its FEs. This straightforwardly allows us to propagate the ontological semantic types (see Sect 6.2.1) on the Parent frame and its FEs downward to the Child frame and its FEs. However, what may not yet be apparent is the fact that the FE bindings in all frame-to-frame relations are equivalent to the Inheritance FE bindings, regardless of the type of relation. This means that normal semantic types on FEs can be propagated down the hierarchy along every type of relation. Types are propagated explicitly in the current OWL representation of the FrameNet data. Because we cannot anticipate all of the Semantic Types that will be useful for tagging FEs, it will certainly also be desirable to categorize the fillers of our FEs using WordNet (or a similar resource). Just as with the pre-marked semantic types applied by the FrameNet team, whatever information is gathered on fillers of an FE in one frame can be propagated to all FEs which are connected to it by any frame-to-frame relation.

Table of Content

  1. Classes
  2. Object Properties
  3. Data Properties
  4. Annotation Properties
  5. General Axioms
  6. Namespace Declarations

Classes

annotation setc back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/AnnotationSet

(Semantically) an annotation set for a sentence generally describes an instance of the subclass associated with an LU as well as instances of each of its associated FE classes.
has super-classes
thingc
annotation set frameop some framec
annotation set l uop some lex unitc
has layerop some layerc
annotation set cxn i ddp some int
annotation set cxn namedp some string
annotation set statusdp some string
annotation set i ddp exactly 1
annotation set c datedp exactly 1
is in domain of
annotatio for sentenceop, annotation set c datedp, annotation set cxn i ddp, annotation set cxn namedp, annotation set frameop, annotation set i ddp, annotation set l uop, annotation set statusdp, has layerop
is in range of
frame of annotation setop, has annotation setop, layer annotation setop, lexicla unit of annotation setop
is disjoint with
corp docc, documentc, f e core setc, framec, frame elementc, full text annotationc, headerc, labelc, layerc, lex unitc, lexemec, sem typec, sentencec, sentence countc

corp docc back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/CorpDoc

has super-classes
thingc
has documentop some documentc
corp doc i ddp exactly 1
corp doc namedp exactly 1
is in domain of
corp doc i ddp, corp doc namedp, corpus document headerop, corpus document of sentenceop, has documentop
is in range of
from corpus documentop, has corp docop, sentence in corp docop
is disjoint with
annotation setc, documentc, f e core setc, framec, frame elementc, full text annotationc, headerc, labelc, layerc, lex unitc, lexemec, sem typec, sentencec, sentence countc

documentc back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/Document

has super-classes
thingc
document i ddp exactly 1
document descriptiondp exactly 1
is in domain of
contain sentenceop, document descriptiondp, document i ddp, from corpus documentop
is in range of
has documentop, sentence in documentop
is disjoint with
annotation setc, corp docc, f e core setc, framec, frame elementc, full text annotationc, headerc, labelc, layerc, lex unitc, lexemec, sem typec, sentencec, sentence countc

f e core setc back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/FECoreSet

In our annotation practice, we often find that some groups of FEs seem to act like sets, in that the presence of any member of the set is sufficient to satisfy a semantic valence of the predicator. We refer to such a group of FEs as a coreness set, or CoreSet. For instance, Source, Path, and Goal are core FEs in the various motion frames in the database. However, although possible, it is not necessary, and in fact unusual, for all three FEs to co-occur, as in example (14). Sentences in many motion frames can be informationally complete and pragmatically felicitous with just one or two of the FEs expressed, as shown in (15)-(18). (14) Fred went [from Berkeley Source] [across North America and the Atlantic Ocean Path] [to Paris Goal]. (15) Martha hiked [from Berkeley Source] [to Oakland Goal]. (16) Elaine walked [to Monterey Goal]. (17) I saw Peter sneak [past the guard Path]. (18) Juan was walking [out of the office Source] when I arrived. FrameNet's normal annotation practice demands that we account for all core FEs and we could keep track of the un-instantiated FEs in the example sentences above by using null-instantiation labels as described in section (3.2.3). However, we prefer to group the FEs in CoreSets and not mark null instantiation for each member FE in cases where the FEs have an informational and conceptual interdependence. Source, Path, and Goal, for instance, are clearly related via a notion that we might call 'full path'. By contrast, omission of the Ingestibles for eat in the Ingestion frame is not related to the presence or absence of any other frame element. The sentence I'm eating __ (with my friends/in the kitchen/now) is acceptable with or without any of the frame elements given in parentheses expressed.
has super-classes
thingc
has memberop some frame elementc
is frame element core set ofop exactly 1 framec
is in domain of
has memberop, is frame element core set ofop
is in range of
has f ecore setop, in core setop
is disjoint with
annotation setc, corp docc, documentc, framec, frame elementc, full text annotationc, headerc, labelc, layerc, lex unitc, lexemec, sem typec, sentencec, sentence countc

framec back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/Frame

(Semantically) frames describe classes of situations. Inheritance has a special place among the frame relations. It is to be interpreted as a subtype or “is-a” relation between frame classes. This constrains the Child frame to have all of the properties of the Parent frame. Although it is difficult to generalize across all of the relations, it is usually true that an instance of a Sub frame implies the existence of an instance of a Super frame. In the case of a Theft, which inherits from Committing crime, an instance of Theft is obviously an instance of Committing crime. For the Precedes relation, however, this is not exactly true. For the Subframe relation, the existence of a Subframe instance does imply the relevance of a Complex frame instance, but the reverse is not true. So, for example, if there is an instance of the Sentencing frame, then we can instantiate an instance of the Criminal process frame. We can then also instantiate all of the subframes of Criminal process which must precede Sentencing, including Trial, Arraignment, etc., but we cannot instantiate the Appeal subframe of Criminal process which follows Sentencing.
has super-classes
thingc
has frame elementop some frame elementc
has lex unitop some lex unitc
frame i ddp exactly 1
frame c bydp exactly 1
frame c datedp exactly 1
frame namedp exactly 1
is in domain of
frame c bydp, frame c datedp, frame headerop, frame i ddp, frame namedp, frame of annotation setop, has causativeop, has f ecore setop, has frame elementop, has frame relationop, has inchoativeop, has lex unitop, has subframeop, inherits fromop, is causative ofop, is inchoative ofop, is inherited byop, is perspectivized inop, is preceded byop, is used byop, perspective onop, precedesop, see alsoop, subframe ofop, usesop
is in range of
annotation set frameop, framal lex unit ofop, frame element ofop, has causativeop, has frameop, has frame relationop, has inchoativeop, has subframeop, inherits fromop, is causative ofop, is frame element core set ofop, is inchoative ofop, is inherited byop, is perspectivized inop, is preceded byop, is used byop, lex unit of frameop, perspective onop, precedesop, see alsoop, subframe ofop, usesop
is disjoint with
annotation setc, corp docc, documentc, f e core setc, frame elementc, full text annotationc, headerc, labelc, layerc, lex unitc, lexemec, sem typec, sentencec, sentence countc

frame elementc back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/FrameElement

Extrathematic frame elements Extra-thematic FEs have a considerably different interpretation from all other FE types. Normal FEs (barring Coresets or Excludes relations) must always be logically present for the frame to make sense. Extra-thematic FEs, however, independently evoke a different frame from from the one they are listed in. The Extra-thematic FE itself fills one of the FEs of this frame, and the other FEs are filled by various frame elements of the original target word according to heuristics which must be separately specified for each Extra-thematic FE. For example, in 44, evoking the Ride vehicles frame, the Cotheme FE evokes an additional instance of Motion whose Theme FE is filled by the Cotheme, and whose Path and other FEs are co-identified with the instance of Ride vehicles. Thus both “I” and “her” are described as moving to school in this example. (44) I rode to school [with her Cotheme] all the time. (Semantically) non-Extrathematic FEs are classes that are arguments of the Frame classes.
has super-classes
thingc
f e i ddp exactly 1
f e abbrevdp exactly 1
f e c bydp exactly 1
f e c datedp exactly 1
f e core typedp exactly 1
f e core typedp exactly 1
f e namedp exactly 1
is in domain of
excludesop, f e abbrevdp, f e c bydp, f e c datedp, f e core typedp, f e i ddp, f e namedp, frame element labelop, frame element ofop, has f e relationop, has sub f eop, has super f eop, in core setop, incorporated in lexical unitop, is excluded byop, is required byop, requiresop
is in range of
excludesop, has f e relationop, has frame elementop, has memberop, has sub f eop, has super f eop, incorporated f eop, is excluded byop, is required byop, label f eop, requiresop
is disjoint with
annotation setc, corp docc, documentc, f e core setc, framec, full text annotationc, headerc, labelc, layerc, lex unitc, lexemec, sem typec, sentencec, sentence countc

full text annotationc back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/FullTextAnnotation

Formally, FrameNet annotations are constellations of triples that make up the frame element realization for each annotated sentence, each consisting of a frame element (for example, Food), a grammatical function (say, Object) and a phrase type (say, NP). We think of these three types of annotation on each tagged frame element as layers. The work can be divided into two kinds according to the way in which sentences are chosen for annotation. In the 'lexicographic annotation' mode, our main focus is on the goal of recording the range of semantic and syntactic combinatory possibilities (valences) of each word in each of its senses. To that end, we extract sentences from the different texts of a corpus because they contain a predetermined target LU. Then we annotate a selection of the extracted sentences in respect to that particular LU. In another kind of work that represents a much smaller percentage of our overall annotations, we annotate running text. This is called 'full-text annotation'. Full-text annotation differs from sentence annotation mostly in that the sentences are chosen for us, so to speak, by the author of the text. The annotation of running text is technically possible thanks to the annotation layering technique: FN lexicographers can one by one declare each word in a sentence a target, select a frame relative to which the new target is to be annotated, get a new set of annotation layers (frame element, grammatical function, phrase type) and appropriate frame element tags, and then annotate the relevant constituents. Before going further into the details of annotation, let us briefly consider the Revenge frame, which will figure as an example frame repeatedly in this chapter. The definition of this frame follows: 'An Avenger performs some Punishment on an Offender as a response to an earlier action, the Injury, that was inflicted on an Injured party. The Avenger need not be identical to the Injured party but needs to consider the prior action of the Offender a wrong. Importantly, the punishment of the Offender by the Avenger is seen as justified by individual or group opinion rather than by law.' Thus, the frame elements in the Revenge frame are Avenger, Punishment, Offender, Injury, and Injured party. Lexical units in this frame include avenge.v, avenger.n, get even.v, retaliate.v, retaliation.n, retribution.n, retributive.a, retributory.a, revenge.v, revenge.n, revengeful.a, revenger.n, vengeance.n, vengeful.a, and vin- dictive.a. Some example sentences with the lexical unit avenge are given here. (1) [His brothers Avenger] avenged [him Injured party]. (2) With this, [El Cid Agent] at once avenged [the death of his son Injury]. (3) [Hook Avenger] tries to avenge [himself Injured party] [on Peter Pan Offender] [by becoming a second and better father Punishment].
has super-classes
thingc
has headerop some headerc
has sentenceop some sentencec
is in domain of
has headerop, has sentenceop
is in range of
header full text annotationop, sentence full text annotationop
is disjoint with
annotation setc, corp docc, documentc, f e core setc, framec, frame elementc, headerc, labelc, layerc, lex unitc, lexemec, sem typec, sentencec, sentence countc

generic f ec back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/GenericFE

has super-classes
thingc

headerc back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/Header

has super-classes
thingc
has corp docop some corp docc
has frameop some framec
is in domain of
has corp docop, has frameop, header full text annotationop
is in range of
corpus document headerop, frame headerop, has headerop
is disjoint with
annotation setc, corp docc, documentc, f e core setc, framec, frame elementc, full text annotationc, labelc, layerc, lex unitc, lexemec, sem typec, sentencec, sentence countc

labelc back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/Label

has super-classes
thingc
label f eop some frame elementc
label enddp some int
label c bydp exactly 1
label itypedp exactly 1
label namedp exactly 1
label startdp exactly 1
is in domain of
label c bydp, label enddp, label f eop, label itypedp, label layerop, label namedp, label startdp
is in range of
frame element labelop, has labelop
is disjoint with
annotation setc, corp docc, documentc, f e core setc, framec, frame elementc, full text annotationc, headerc, layerc, lex unitc, lexemec, sem typec, sentencec, sentence countc

layerc back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/Layer

has super-classes
thingc
has labelop some labelc
layer namedp exactly 1
layer rankdp exactly 1
is in domain of
has labelop, layer annotation setop, layer namedp, layer rankdp
is in range of
has layerop, label layerop
is disjoint with
annotation setc, corp docc, documentc, f e core setc, framec, frame elementc, full text annotationc, headerc, labelc, lex unitc, lexemec, sem typec, sentencec, sentence countc

lex unitc back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/LexUnit

(Semantically) LUs are subclasses of the Frames. Except for the rare LUs with the Semantic Type Biframal LU or LUs in frames which are marked Non-perspectivalized, all LUs of a frame have a semantics which is best described as a subtype of the semantics of the frame. With these caveats, one may thus consider LU membership in a frame to be an identical relationship to Inheritance from a frame. All LUs in a frame must have the same number and types of frame elements in both explicit and implicit (NI) contexts.
has super-classes
thingc
has lexemeop some lexemec
has sentence countop some sentence countc
l u statusdp some string
l u i ddp exactly 1
l u p o sdp exactly 1
l u c bydp exactly 1
l u c datedp exactly 1
l u lemma i ddp exactly 1
l u namedp exactly 1
is in domain of
has lexemeop, has sentence countop, incorporated f eop, l u c bydp, l u c datedp, l u i ddp, l u lemma i ddp, l u namedp, l u p o sdp, l u statusdp, lex unit of frameop, lexicla unit of annotation setop
is in range of
annotation set l uop, generic lex unitop, has lex unitop, incorporated in lexical unitop, lexeme of lexical unitop, sentence count of lexical unitop
is disjoint with
annotation setc, corp docc, documentc, f e core setc, framec, frame elementc, full text annotationc, headerc, labelc, layerc, lexemec, sem typec, sentencec, sentence countc

lexemec back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/Lexeme

has super-classes
thingc
lexeme p o sdp exactly 1
lexeme break beforedp exactly 1
lexeme headworddp exactly 1
lexeme namedp exactly 1
lexeme orderdp exactly 1
is in domain of
lexeme break beforedp, lexeme headworddp, lexeme namedp, lexeme of lexical unitop, lexeme orderdp, lexeme p o sdp
is in range of
has lexemeop
is disjoint with
annotation setc, corp docc, documentc, f e core setc, framec, frame elementc, full text annotationc, headerc, labelc, layerc, lex unitc, sem typec, sentencec, sentence countc

sem typec back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/SemType

The general use of semantic types in the FrameNet project is to record information that is not representable in our frame and frame element hierarchies. In this section there is a detailed description of each major category of the semantic type hierarchy, which is broadly split by function. In specific, the functions we currently employ semantic types for are: • Indicating the basic typing of fillers of frame elements, e.g. “Sentient” for the Cognizer FE. These basic types are constrained by the frame hierarchy (see section 6.3.5.1), but not predictable from it since frame elements which are arbitrarily far away according to the frame hierarchy, such as the Experiencer of Perception body and the Perpetrator of the Piracy frame, are often marked as the same semantic type (in this case, Sentient). This kind of semantic type is designed primarily to aid frame parsing and automatic FE recognition. • Useful, functional marking on frames, such as the type “Non-lexical” on frames which are present purely to participate in Inheritance, Subframe, or Using relations with other frames. This kind of property is actually a meta-description, not a fact about the semantics of the frame at all, and thus independent of the hierarchy. In fact, a frame which in English is Non-lexical might well have associated LUs in another language. • Marking important dimensions of semantic variation among the lexical units in a frame that are not related to the kind of semantic combinatorial possibilities that we use for making frame distinctions (see Chapter 2). For instance, in the Judgment frame the difference between LUs such as praise.v and criticize.v in terms of the negative versus positive evaluation of the Evaluee is marked with the semantic types Positive judgment and Negative judgment, respectively. The most interesting function of semantic types for human users is the third one, recording important semantic differences between lexical units that recur within several frames. For example, “Positive judgement” and “Negative judgement” semantic types, indicating the speaker’s attitude toward a situation, can be applied to lexical units across a range of frames. (Note that the term speaker may either refer to a frame element such as Speaker or Cognizer, or to the author of the utterance containing the lexical unit.) We capture the distinction by marking LUs like the aforementioned Judgment verb praise, the Experiencer subj verb like, and the Frugality adjective generous as “Positive judgement” and, by contrast, marking “Negative judgement” on some other words from the same frames, e.g. criticize and hate, and stingy. For more description and further examples, see the following subsections.
has super-classes
thingc
sem type i ddp exactly 1
sem type abbrevdp exactly 1
sem type namedp exactly 1
is in domain of
has subtypeop, has super typeop, is semantic type ofop, sem type abbrevdp, sem type i ddp, sem type namedp
is in range of
has sem typeop, has subtypeop, has super typeop
is disjoint with
annotation setc, corp docc, documentc, f e core setc, framec, frame elementc, full text annotationc, headerc, labelc, layerc, lex unitc, lexemec, sentencec, sentence countc

sentencec back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/Sentence

has super-classes
thingc
sentence in corp docop some corp docc
sentence in documentop some documentc
sentence parag nodp some int
sentence sent nodp some int
textdp some string
sentence i ddp exactly 1
sentence a posdp exactly 1
is in domain of
has annotation setop, sentence a posdp, sentence full text annotationop, sentence i ddp, sentence in corp docop, sentence in documentop, sentence parag nodp, sentence sent nodp, textdp
is in range of
annotatio for sentenceop, contain sentenceop, corpus document of sentenceop, has sentenceop
is disjoint with
annotation setc, corp docc, documentc, f e core setc, framec, frame elementc, full text annotationc, headerc, labelc, layerc, lex unitc, lexemec, sem typec, sentence countc

sentence countc back to ToC or Class ToC

IRI: https://w3id.org/framester/framenet/tbox/SentenceCount

has super-classes
thingc
sentence count annotateddp some int
sentence count totaldp some int
is in domain of
sentence count annotateddp, sentence count of lexical unitop, sentence count totaldp
is in range of
has sentence countop
is disjoint with
annotation setc, corp docc, documentc, f e core setc, framec, frame elementc, full text annotationc, headerc, labelc, layerc, lex unitc, lexemec, sem typec, sentencec

Object Properties

annotatio for sentenceop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/annoForSentence

has domain
annotation setc
has range
sentencec
is inverse of
has annotation setop

annotation set frameop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/annotationSetFrame

has domain
annotation setc
has range
framec
is inverse of
frame of annotation setop

annotation set l uop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/annotationSetLU

has domain
annotation setc
has range
lex unitc
is inverse of
lexicla unit of annotation setop

contain sentenceop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/containsSentence

has domain
documentc
has range
sentencec
is inverse of
sentence in documentop

corpus document headerop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/corpDocHeader

has domain
corp docc
has range
headerc
is inverse of
has corp docop

corpus document of sentenceop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/corpDocOfSentence

has domain
corp docc
has range
sentencec
is inverse of
sentence in corp docop

excludesop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/excludes

In some cases, if one of the FEs in a group of conceptually related FEs shows up, no other FE from that group can. Again, in the Attaching frame, if Items occurs, then Item and Goal are excluded. In this situation, we say that Items excludes Item and Goal. (21) The robbers tied [his ankles Items] together. The above Excludes-relation in the Attaching frame is an instance of a much more common pattern of alternation between a symmetric/reciprocal and an asymmetric construal of events or states involving two parties. In most frames, where the alternation is possible, the names of the frame elements reflect the underlying alternation between reciprocal and asymmetric construal. For instance, in the Similarity frame with lexical units such as similar, different, etc. we have the frame elements Entity_1 and Entity_2, and Entities. Usually, one is allowed to infer equal participation in the event or state by the grammatically less profiled participant (Participant_2). However, since in the case of Attaching, the Goal (which would be Item_2 under our normal naming scheme) is not readily understood as itself being secured or immobilized via attachment to the Item on the asymmetric construal, we selected a name that reflects the fact that the usual inference to equal status for Participant_2 in the asymmetric construal is not warranted. The Excludes relation also manifests in frames where an event can be brought about either by an intentional Agent or by a Cause event. Consider the following examples from the Placing frame. (22) [The same flood tide that had brought such a good harvest of tiles Cause] heaped a mass of driftwood onto the Reach. (23) [Bill Agent] deposited the bag of croissants and the Financial Times carelessly on the hall table. The two sentences represent two different construals of Placing scenes. Sentence (22) focuses on an event as causing the change in location of the Theme, whereas sentence (23) focuses on an Agent who through their involvement in an unspecified event, most likely an intentional action involving his hands and body, causes the change of location of the Theme. The two construals are incompatible (since there is only one subject slot) and the frame elements Agent and Cause stand in an Excludes relation to each other.8 Another clear instance of the Excludes relation between frame elements occurs in the Evading frame, where an Evader moves under its own power to thereby avoid Capture or contact with a Pursuer. The Capture is an actual or hypothetical event in which the Pursuer takes physical control of the Evader. The Capture frame element and the Pursuer are thus clearly interrelated but only one of them can appear as a dependent of a target in the Evading frame. (24) Sheriff's officials said they apprehended a gang member after he evaded [them Pursuer]. (25) He had successfully evaded [arrest Capture]. Finally, note that the Excludes relation strictly applies only to the direct syntactic dependents of a target word, that is, to first layer annotation. Frame elements that exclude each other may co-occur in an annotation set if they appear on separate annotation layers. (26) Perkins McLain evaded [capture [through Spain Pursuer] Capture] . (27) The discussions [between [Miller Interlocutor_1] and [the dean Interlocutor_2] Interlocutors ] went nowhere. In (26), information about the Pursuer is expressed inside the Capture frame element in a prepositional phrase dependent of the noun capture. In (27), the two sides of the discussion, Interlocutor_1 and Interlocutor_2 are expressed within the coordinate NP that encodes the Interlocutors frame element.
has super-properties
has f e relationop
has domain
frame elementc
has range
frame elementc
is inverse of
is excluded byop

framal lex unit ofop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/framalLexUnitOf

has domain
framal lex unitc
has range
framec

frame element labelop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/FELabel

has domain
frame elementc
has range
labelc
is inverse of
label f eop

frame element ofop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/frameElementOf

has domain
frame elementc
has range
framec
is inverse of
has frame elementop

frame headerop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/frameHeader

has domain
framec
has range
headerc
is inverse of
has frameop

frame of annotation setop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/frameOfAnnotationSet

has domain
framec
has range
annotation setc
is inverse of
annotation set frameop

from corpus documentop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/fromCorpDoc

has domain
documentc
has range
corp docc
is inverse of
has documentop

generic lex unitop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/genericLexUnit

has domain
framal lex unitc
has range
lex unitc

has annotation setop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasAnnotationSet

has domain
sentencec
has range
annotation setc
is inverse of
annotatio for sentenceop

has causativeop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasCausative

has super-properties
has frame relationop
has domain
framec
has range
framec
is inverse of
is causative ofop

has corp docop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasCorpDoc

has domain
headerc
has range
corp docc
is inverse of
corpus document headerop

has documentop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasDocument

has domain
corp docc
has range
documentc
is inverse of
from corpus documentop

has f e relationop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasFERelation

Any relation between frame elements.

has characteristics: symmetric

has sub-properties
excludesop, has sub f eop, has super f eop, is excluded byop, is required byop, requiresop
has domain
frame elementc
has range
frame elementc
is inverse of
has f e relationop, has f e relationop

has f ecore setop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasFEcoreSet

has characteristics: inverse functional

has domain
framec
has range
f e core setc
is inverse of
is frame element core set ofop

has frameop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasFrame

has domain
headerc
has range
framec
is inverse of
frame headerop

has frame elementop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasFrameElement

has domain
framec
has range
frame elementc
is inverse of
frame element ofop

has frame relationop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasFrameRelation

Any relation between frames. Each frame relation in the FrameNet data is a directed (asymmetric) relation between two frames, where one frame (the less dependent, or more abstract) can be called the Super frame and another (the more dependent, or less abstract) can be called the Sub frame. We give a more specific, informative name to the Super and Sub frames for each relation, as shown in Table 6.1 below. Role names for the specialized relations: Relation Sub Super Inheritance Child Parent Perspective on Perspectivized Neutral Subframe Component Complex Precedes Later EarlierState Inchoative of Inchoative State Causative of Causative Inchoative/State Using Child Parent See also ReferringEntry MainEntry

has characteristics: symmetric

has sub-properties
has causativeop, has inchoativeop, has subframeop, inherits fromop, is causative ofop, is inchoative ofop, is inherited byop, is perspectivized inop, is preceded byop, is used byop, perspective onop, precedesop, see alsoop, subframe ofop, usesop
has domain
framec
has range
framec
is inverse of
has frame relationop, has frame relationop

has headerop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasHeader

has domain
full text annotationc
has range
headerc
is inverse of
header full text annotationop

has inchoativeop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasInchoative

has super-properties
has frame relationop
has domain
framec
has range
framec
is inverse of
is inchoative ofop

has labelop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasLabel

has domain
layerc
has range
labelc
is inverse of
label layerop

has layerop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasLayer

has domain
annotation setc
has range
layerc
is inverse of
layer annotation setop

has lex unitop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasLexUnit

has domain
framec
has range
lex unitc
is inverse of
lex unit of frameop

has lexemeop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasLexeme

has domain
lex unitc
has range
lexemec
is inverse of
lexeme of lexical unitop

has memberop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasMember

has domain
f e core setc
has range
frame elementc
is inverse of
in core setop

has sem typeop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasSemType

has domain
framec or frame elementc or lex unitc
has range
sem typec
is inverse of
is semantic type ofop

has sentenceop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasSentence

has domain
full text annotationc
has range
sentencec
is inverse of
sentence full text annotationop

has sentence countop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasSentenceCount

has domain
lex unitc
has range
sentence countc
is inverse of
sentence count of lexical unitop

has sub f eop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasSubFE

We have no explicit treatment of the idea of proto-frame elements, of which other frame elements are more specialized expressions. In cases like (28), we would prefer not to have to pick either specifically Agent or Cause as constructionally null instantiated, since the context might not provide enough information to resolve that question. Instead we would make reference to a superordinate frame element (call it *Force) that is vague about intentionality and the event-person distinction. Likewise in (29), where B answers a question about a new employee, we would prefer to use a superordinate frame element (which might be named *Field in this case), rather than choosing among the frame elements Role, Skill, Knowledge, or Focal participant for constructional null instantiation relative to the predicate good in the Expertise frame. (28) The car got damaged while parked outside of our house. (29) A. How’s Susan working out? B. She’s very good. Having an explicit representation of proto-frame elements would also be useful in dealing with certain linguistic expressions that seem to instantiate the superordinate proto-frame element rather than one of its more specific manifestations. Consider the phrase trench to trench in (30): it does not refer to the Source or Goal of a Path but neither does it refer to a middle Path which would be compatible with the specification of a final Goal. A proto-frame element Full path would provide the most adequate treatment. (30) He crawled [trench to trench], looking for some sign of Stephen. Another use for Proto-frame elements involves inheritance relations. In some cases, an inheriting frame will allow only one FE from an Excludes or CoreSet group in the parent frame. Superficially, this violates the rule that requires child frames to have a corresponding FE for each core/peripheral FE of the parent. In a deeper sense, however, inheriting only one member of a frame element set should be permitted on the understanding of inheritance as subtyping. This is so because the child frame is fulfilling every constraint of the parent, merely adding a constraint that prevents one of the construals possible in the more generic case. If we state the frame element restriction on inheritance so that it pays attention only to the most generic level of FEs, then mappings from subsidiary FEs are allowable, but not required. This would make it possible, for instance, to have a *Murder frame (with only agentive causes) as a child frame of the Killing frame (which allows Causes or Agents).
has super-properties
has f e relationop
has domain
frame elementc
has range
frame elementc
is inverse of
has super f eop

has subframeop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasSubframe

Some frames are complex in that they refer to sequences of states and transitions, each of which can itself be separately described as a frame. The separate frames (called subframes) are related to the complex frames via the SubFrame relation. In such cases, frame elements of the complex frame may be identified (mapped) to the frame elements of the subparts, although not all frame elements of one need have any relation to the other. (In this respect, it contrasts with inheritance; see below.) Also, the ordering and other temporal relationships of the subframes can be specified using binary precedence relations. A Suspect is arrested by an Authority on certain Charges, then is arraigned as a Defendant. If at any time the Defendant pleads guilty, then the Defendant is sentenced, otherwise the Defendant first goes to trial. If the Finding after the trial is guilty, then the Defendant is sentenced. In the end, the Defendant is either released or is given a Sentence by a Judge at the sentencing. For each step in the process, there is a separate frame in the database, including Arrest, Arraignment, Trial, Sentencing, and so on. Each of these frames is related to the Criminal process frame via the SubFrame relation in the database. Moreover, subframes (of the same complex frame) are related to each other through their ordering. (See Narayanan et al. (2002) and Scheffczyk et al. (2006).) Note that the FEs of the subframes need not map to those of other subframes. So, in this same group of frames, the Arrest frame includes an Arresting authority which is not included in the Trial frame. Notice that a given subframe may itself be a complex frame. For example, the Trial frame is a subframe of the Criminal process frame, and has its own rich structure, some of which can be decomposed into simpler frames that are related to each other. A Trial is made up of court appearances, and involves opening arguments, presentation of evidence and testimony, and closing arguments. The system of subframe links is also quite complex. At present, the subframe relation is not indicated in every relevant case.
has super-properties
has frame relationop
has domain
framec
has range
framec
is inverse of
subframe ofop

has subtypeop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasSubType

has domain
sem typec
has range
sem typec
is inverse of
has super typeop

has super f eop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasSuperFE

We have no explicit treatment of the idea of proto-frame elements, of which other frame elements are more specialized expressions. In cases like (28), we would prefer not to have to pick either specifically Agent or Cause as constructionally null instantiated, since the context might not provide enough information to resolve that question. Instead we would make reference to a superordinate frame element (call it *Force) that is vague about intentionality and the event-person distinction. Likewise in (29), where B answers a question about a new employee, we would prefer to use a superordinate frame element (which might be named *Field in this case), rather than choosing among the frame elements Role, Skill, Knowledge, or Focal participant for constructional null instantiation relative to the predicate good in the Expertise frame. (28) The car got damaged while parked outside of our house. (29) A. How’s Susan working out? B. She’s very good. Having an explicit representation of proto-frame elements would also be useful in dealing with certain linguistic expressions that seem to instantiate the superordinate proto-frame element rather than one of its more specific manifestations. Consider the phrase trench to trench in (30): it does not refer to the Source or Goal of a Path but neither does it refer to a middle Path which would be compatible with the specification of a final Goal. A proto-frame element Full path would provide the most adequate treatment. (30) He crawled [trench to trench], looking for some sign of Stephen. Another use for Proto-frame elements involves inheritance relations. In some cases, an inheriting frame will allow only one FE from an Excludes or CoreSet group in the parent frame. Superficially, this violates the rule that requires child frames to have a corresponding FE for each core/peripheral FE of the parent. In a deeper sense, however, inheriting only one member of a frame element set should be permitted on the understanding of inheritance as subtyping. This is so because the child frame is fulfilling every constraint of the parent, merely adding a constraint that prevents one of the construals possible in the more generic case. If we state the frame element restriction on inheritance so that it pays attention only to the most generic level of FEs, then mappings from subsidiary FEs are allowable, but not required. This would make it possible, for instance, to have a *Murder frame (with only agentive causes) as a child frame of the Killing frame (which allows Causes or Agents).
has super-properties
has f e relationop
has domain
frame elementc
has range
frame elementc
is inverse of
has sub f eop

has super typeop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/hasSuperType

has domain
sem typec
has range
sem typec
is inverse of
has subtypeop

header full text annotationop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/headerFullTextAnno

has domain
headerc
has range
full text annotationc
is inverse of
has headerop

in core setop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/inCoreSet

has domain
frame elementc
has range
f e core setc
is inverse of
has memberop

incorporated f eop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/incorporatedFE

There are many frames containing verbs which generally involve a particular of frame element, but where some of the verbs incorporate information about that frame element in their definition. Consider, for example, verbs of body movement; typically certain verbs are expected to co-occur with the name of a body part, even when the identity of the body part is clear from the meaning of the verb. A dog wags its tail, people arch their brows, bat their eyes, purse their lips, etc. But in the case of smile, grimace, frown, pout, and scowl, the affected body part is not separately expressed; we say that it is incorporated. Some verbs in this frame can optionally express the expected body part: one can say either She blinked or She blinked her eyes. Likewise, in the Placing frame, many verbs incorporate the Goal FE (i.e. the place where the Theme ends up) such as bag.v, bin.v, bottle.v, box.v, cage.v, crate.v, file.v, garage.v. Note that it is still possible to further specify the incorporated FE explicitly, as in They bottled the wine in custom-made blue bottles, in which case, in custom-made blue bottles is annotated as the Goal FE, as usual. In defining a new LU, one can specify an incorporated FE.
has domain
lex unitc
has range
frame elementc
is inverse of
incorporated in lexical unitop

incorporated in lexical unitop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/incorporatedInLU

There are many frames containing verbs which generally involve a particular of frame element, but where some of the verbs incorporate information about that frame element in their definition. Consider, for example, verbs of body movement; typically certain verbs are expected to co-occur with the name of a body part, even when the identity of the body part is clear from the meaning of the verb. A dog wags its tail, people arch their brows, bat their eyes, purse their lips, etc. But in the case of smile, grimace, frown, pout, and scowl, the affected body part is not separately expressed; we say that it is incorporated. Some verbs in this frame can optionally express the expected body part: one can say either She blinked or She blinked her eyes. Likewise, in the Placing frame, many verbs incorporate the Goal FE (i.e. the place where the Theme ends up) such as bag.v, bin.v, bottle.v, box.v, cage.v, crate.v, file.v, garage.v. Note that it is still possible to further specify the incorporated FE explicitly, as in They bottled the wine in custom-made blue bottles, in which case, in custom-made blue bottles is annotated as the Goal FE, as usual. In defining a new LU, one can specify an incorporated FE.
has domain
frame elementc
has range
lex unitc
is inverse of
incorporated f eop

inherits fromop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/inheritsFrom

This is the strongest relation between frames, corresponding to is-a in many ontologies. With this relation, anything which is strictly true about the semantics of the Parent must correspond to an equally or more specific fact about the Child. This includes Frame Element membership of the frames (except for Extrathematic FEs), most Semantic Types, frame relations to other frames, relationships among the Frame Elements, and Semantic Types on the Frame Elements. Properties of the Parent which are not strictly semantic in nature, such as not being evoked by lexical units (i.e. the Semantic Type Non-lexical frame), being evoked by a particular set of Lexical Units, or having a See also relation to another frame, are not inherited. Also, when there is a Core-set or an Excludes relation among Frame Elements of the Parent, these constitute disjunctive properties of the Parent. The Child frame may legitimately inherit only a subset of these disjunctive Frame Elements.
has super-properties
has frame relationop
has domain
framec
has range
framec
is inverse of
is inherited byop

is causative ofop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/isCausativeOf

We record the especially close and fairly systematic non-inheritance relationships between stative frames and the inchoative and causative frames which refer to them using the frame-to-frame relations Causative of and Inchoative of. Consider the following frames: Position on a scale, Change position on a scale, and Cause change of scalar position. The following sentences illustrate the kind distinction captured in these frames: (1) [Cause change of scalar position] (raise.v) Billie Blount raised taxes on farmers 18 times in 2002! (2) [Change position on a scale] (rise.v) During the Elizabethan age, there was an increased em- phasis on genealogy in the heralds’ work as the gentry class rose in importance. (3) [Position on a scale] (high.a) Most fish from lakes is too high in mercury. Frames which participate in these relations as Causatives should inherit from the Transitive action frame, Inchoatives should inherit from Event, and States from State or Gradable attribute.6 Many of these inheri- tance relations have not yet been made.
has super-properties
has frame relationop
has domain
framec
has range
framec
is inverse of
has causativeop

is excluded byop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/isExcludedBy

has super-properties
has f e relationop
has domain
frame elementc
has range
frame elementc
is inverse of
excludesop

is frame element core set ofop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/isFECoreSetOf

has characteristics: functional

has domain
f e core setc
has range
framec
is inverse of
has f ecore setop

is inchoative ofop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/isInchoativeOf

We record the especially close and fairly systematic non-inheritance relationships between stative frames and the inchoative and causative frames which refer to them using the frame-to-frame relations Causative of and Inchoative of. Consider the following frames: Position on a scale, Change position on a scale, and Cause change of scalar position. The following sentences illustrate the kind distinction captured in these frames: (1) [Cause change of scalar position] (raise.v) Billie Blount raised taxes on farmers 18 times in 2002! (2) [Change position on a scale] (rise.v) During the Elizabethan age, there was an increased em- phasis on genealogy in the heralds’ work as the gentry class rose in importance. (3) [Position on a scale] (high.a) Most fish from lakes is too high in mercury. Frames which participate in these relations as Causatives should inherit from the Transitive action frame, Inchoatives should inherit from Event, and States from State or Gradable attribute.6 Many of these inheri- tance relations have not yet been made.
has super-properties
has frame relationop
has domain
framec
has range
framec
is inverse of
has inchoativeop

is inherited byop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/isInheritedBy

This is the strongest relation between frames, corresponding to is-a in many ontologies. With this relation, anything which is strictly true about the semantics of the Parent must correspond to an equally or more specific fact about the Child. This includes Frame Element membership of the frames (except for Extrathematic FEs), most Semantic Types, frame relations to other frames, relationships among the Frame Elements, and Semantic Types on the Frame Elements. Properties of the Parent which are not strictly semantic in nature, such as not being evoked by lexical units (i.e. the Semantic Type Non-lexical frame), being evoked by a particular set of Lexical Units, or having a See also relation to another frame, are not inherited. Also, when there is a Core-set or an Excludes relation among Frame Elements of the Parent, these constitute disjunctive properties of the Parent. The Child frame may legitimately inherit only a subset of these disjunctive Frame Elements.
has super-properties
has frame relationop
has domain
framec
has range
framec
is inverse of
inherits fromop

is perspectivized inop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/isPerspectivizedIn

This relation is a refinement of the more general Using relation. Perspective on constrains related frames considerably more. The use of this relation indicates the presence of at least two different points-of-view that can be taken on the Neutral frame. For example, the Measure scenario, in which an Entity’s Value for some Attribute is described, can be viewed either from the point-of-view of exact measurement (e.g. “Joey weighed 7 pounds.”) or as a relative measure (e.g. “Joey was heavy.”). The FEs in the two cases are quite different, so the words should not be included in the same frame, but they do make reference to the same scene. The Perspective on relation allows us to refer directly to the scene (encoded by the Neutral Measure scenario frame here) and connect the two. As in this case, the Neutral frame is normally Non-lexical and Non-perspectivalized. A single Neutral frame generally has at least two Perspectivalized frames, but in some cases, words of the Neutral frame are consistent with multiple different points-of-view while the Perspectivalized frame is consistentwithonlyone. Whenever there is a state of affairs that is describable by a frame in a Perspective on relation, all the other frames that are connected to it by the Perspective on relation can also be used to describe the state of affairs. For example, the Commercial transaction frame specifies a complex schema involving an exchange of multiple Themes (the Money and Goods) between the Buyer and Seller, including also two subframes: Commerce goods-transfer and Commerce money-transfer. The Buying frame has a Perspective on relationship with the Commerce goods-transfer subframe in which the Money, Goods, Buyer, and Seller are identified. Some other relations of this type include: • Get a job and Hiring are perspectives of Begin employment • Rope manipulation and Knot creation are perspectives on Knot creation scenario Further note that it is quite common for a frame to inherit from one frame and be a perspective on another. An example of this is again provided by the Commerce buy frame, which inherits the Getting frame but is a perspective on the Commerce goods transfer frame. An act of buying is a sub-type of getting, which justifies the inheritance relation to Getting. Buying is an event that only occurs when the situation (the Commerce goods transfer) is also describable as selling. For that reason, it (and the Commerce sell) is connected to the Commerce goods transfer frame via a Perspective on relation.
has super-properties
has frame relationop
has domain
framec
has range
framec
is inverse of
perspective onop

is preceded byop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/isPrecededBy

This relation occurs only between two Component frames of a single Complex frame, i.e. as extra information associated with a set of Subframe relations. It specifies the sequence of states and events that are definitional for a certain state-of-affairs. Most Subframe relations will naturally have precedence relations, as can be seen in the foregoing diagram of the subframes of the Criminal process frame, in which the Precedes relations are indicated by the black lateral arrows. This is the only frame relation for which cycles are allowed. For example, in the subframes of the Sleep wake cycle frame, Being awake precedes Fall asleep, which precedes Sleep, which precedes Waking up or Getting up, which in turn precedes the first frame, Being awake.
has super-properties
has frame relationop
has domain
framec
has range
framec
is inverse of
precedesop

is required byop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/isRequiredBy

has super-properties
has f e relationop
has domain
frame elementc
has range
frame elementc
is inverse of
requiresop

is semantic type ofop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/isSemTypeOf

has domain
sem typec
has range
framec or frame elementc or lex unitc
is inverse of
has sem typeop

is used byop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/isUsedBy

Often a particular frame makes reference in a very general kind of way to the structure of a more abstract, schematic frame. Since the creation of the more specific Perspective on relation, the Using relation is used almost exclusively for cases in which a part of the scene evoked by the Child refers to the Parent frame. For example, Volubility uses the Communication frame, since Volubility describes a quantification of communication events. It is possible for a frame to use more than one frame. An example of this situation is the Judg- ment communication frame. It uses both the Judgment frame and the Statement frame. The Judgment communication frame does not inherit Judgment because it is not a simple subtype of a purely cognitive state. Judgment communication does not inherit Statement either since it distributes the content of the Statement frame’s Message frame element over two frame elements, Evaluee and Reason.
has super-properties
has frame relationop
has domain
framec
has range
framec
is inverse of
usesop

label f eop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/label_FE

has domain
labelc
has range
frame elementc
is inverse of
frame element labelop

label layerop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/labelLayer

has domain
labelc
has range
layerc
is inverse of
has labelop

layer annotation setop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/layerAnnoSet

has domain
layerc
has range
annotation setc
is inverse of
has layerop

lex unit of frameop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/lexUnitFrame

has domain
lex unitc
has range
framec
is inverse of
has lex unitop

lexeme of lexical unitop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/lexemeLU

has domain
lexemec
has range
lex unitc
is inverse of
has lexemeop

lexicla unit of annotation setop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/LUOfAnnotationSet

has domain
lex unitc
has range
annotation setc
is inverse of
annotation set l uop

perspective onop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/perspectiveOn

This relation is a refinement of the more general Using relation. Perspective on constrains related frames considerably more. The use of this relation indicates the presence of at least two different points-of-view that can be taken on the Neutral frame. For example, the Measure scenario, in which an Entity’s Value for some Attribute is described, can be viewed either from the point-of-view of exact measurement (e.g. “Joey weighed 7 pounds.”) or as a relative measure (e.g. “Joey was heavy.”). The FEs in the two cases are quite different, so the words should not be included in the same frame, but they do make reference to the same scene. The Perspective on relation allows us to refer directly to the scene (encoded by the Neutral Measure scenario frame here) and connect the two. As in this case, the Neutral frame is normally Non-lexical and Non-perspectivalized. A single Neutral frame generally has at least two Perspectivalized frames, but in some cases, words of the Neutral frame are consistent with multiple different points-of-view while the Perspectivalized frame is consistentwithonlyone. Whenever there is a state of affairs that is describable by a frame in a Perspective on relation, all the other frames that are connected to it by the Perspective on relation can also be used to describe the state of affairs. For example, the Commercial transaction frame specifies a complex schema involving an exchange of multiple Themes (the Money and Goods) between the Buyer and Seller, including also two subframes: Commerce goods-transfer and Commerce money-transfer. The Buying frame has a Perspective on relationship with the Commerce goods-transfer subframe in which the Money, Goods, Buyer, and Seller are identified. Some other relations of this type include: • Get a job and Hiring are perspectives of Begin employment • Rope manipulation and Knot creation are perspectives on Knot creation scenario Further note that it is quite common for a frame to inherit from one frame and be a perspective on another. An example of this is again provided by the Commerce buy frame, which inherits the Getting frame but is a perspective on the Commerce goods transfer frame. An act of buying is a sub-type of getting, which justifies the inheritance relation to Getting. Buying is an event that only occurs when the situation (the Commerce goods transfer) is also describable as selling. For that reason, it (and the Commerce sell) is connected to the Commerce goods transfer frame via a Perspective on relation.
has super-properties
has frame relationop
has domain
framec
has range
framec
is inverse of
is perspectivized inop

precedesop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/precedes

This relation occurs only between two Component frames of a single Complex frame, i.e. as extra information associated with a set of Subframe relations. It specifies the sequence of states and events that are definitional for a certain state-of-affairs. Most Subframe relations will naturally have precedence relations, as can be seen in the foregoing diagram of the subframes of the Criminal process frame, in which the Precedes relations are indicated by the black lateral arrows. This is the only frame relation for which cycles are allowed. For example, in the subframes of the Sleep wake cycle frame, Being awake precedes Fall asleep, which precedes Sleep, which precedes Waking up or Getting up, which in turn precedes the first frame, Being awake.
has super-properties
has frame relationop
has domain
framec
has range
framec
is inverse of
is preceded byop

requiresop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/requires

In some cases, the occurrence of one core FE requires that another core FE occur as well. To illustrate, in the Attaching frame Item, Goal, and Items all are core FEs. If Item occurs, then Goal is required, as shown below, where the sentence without a Goal is unacceptable. In this situation, we mark a Requires relation between the two frame elements. (19) The robbers tied [Paul Item] [to his chair Goal]. (20) * The robbers tied [Paul Item]. The Requires relation occurs in almost all frames that have a construal alternation between a symmetric construal, when a single frame element name is used, and an asymmetric construal, when two frame elements with names of the are used. In the former case a simple name of the form [FENAME]s is used and in the latter, two FEs of the form [FENAME]_1 and [FENAME]_2 are used. Some sample frames are Compatibility, Chatting, and Similarity; there are many more.
has super-properties
has f e relationop
has domain
frame elementc
has range
frame elementc
is inverse of
is required byop

see alsoop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/seeAlso

In cases where there are groups of frames which are similar and should be carefully differentiated, compared, and contrasted, each of the frames in question has a SeeAlso relation with a representative member of the group. In the frame definition of the representative member, there will be a comparison which will contrast the frames to make clear the intended boundaries between them. For example, since the Scrutiny and Seeking frames are similar, there is a SeeAlso relation from Scrutiny to Seeking, and text in the Seeking frame that explains the difference. This relationship does not imply any particular relationship between the Frame Elements or subframes of the frames involved.
has super-properties
has frame relationop
has domain
framec
has range
framec

sentence count of lexical unitop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/sentenceCountLU

has domain
sentence countc
has range
lex unitc
is inverse of
has sentence countop

sentence full text annotationop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/sentenceFullTextAnno

has domain
sentencec
has range
full text annotationc
is inverse of
has sentenceop

sentence in corp docop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/sentenceInCorpDoc

has domain
sentencec
has range
corp docc
is inverse of
corpus document of sentenceop

sentence in documentop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/sentenceInDocument

has domain
sentencec
has range
documentc
is inverse of
contain sentenceop

subframe ofop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/subframeOf

Some frames are complex in that they refer to sequences of states and transitions, each of which can itself be separately described as a frame. The separate frames (called subframes) are related to the complex frames via the SubFrame relation. In such cases, frame elements of the complex frame may be identified (mapped) to the frame elements of the subparts, although not all frame elements of one need have any relation to the other. (In this respect, it contrasts with inheritance; see below.) Also, the ordering and other temporal relationships of the subframes can be specified using binary precedence relations. To illustrate, consider the complex Criminal process frame. A Suspect is arrested by an Authority on certain Charges, then is arraigned as a Defendant. If at any time the Defendant pleads guilty, then the Defendant is sentenced, otherwise the Defendant first goes to trial. If the Finding after the trial is guilty, then the Defendant is sentenced. In the end, the Defendant is either released or is given a Sentence by a Judge at the sentencing. For each step in the process, there is a separate frame in the database, including Arrest, Arraignment, Trial, Sentencing, and so on. Each of these frames is related to the Criminal process frame via the SubFrame relation in the database. Moreover, subframes (of the same complex frame) are related to each other through their ordering. (See Narayanan et al. (2002) and Scheffczyk et al. (2006).) Note that the FEs of the subframes need not map to those of other subframes. So, in this same group of frames, the Arrest frame includes an Arresting authority which is not included in the Trial frame. Notice that a given subframe may itself be a complex frame. For example, the Trial frame is a subframe of the Criminal process frame, and has its own rich structure, some of which can be decomposed into simpler frames that are related to each other. A Trial is made up of court appearances, and involves opening arguments, presentation of evidence and testimony, and closing arguments. The system of subframe links is also quite complex. At present, the subframe relation is not indicated in every relevant case.
has super-properties
has frame relationop
has domain
framec
has range
framec
is inverse of
has subframeop

usesop back to ToC or Object Property ToC

IRI: https://w3id.org/framester/framenet/tbox/uses

Often a particular frame makes reference in a very general kind of way to the structure of a more abstract, schematic frame. Since the creation of the more specific Perspective on relation, the Using relation is used almost exclusively for cases in which a part of the scene evoked by the Child refers to the Parent frame. For example, Volubility uses the Communication frame, since Volubility describes a quantification of communication events. It is possible for a frame to use more than one frame. An example of this situation is the Judg- ment communication frame. It uses both the Judgment frame and the Statement frame. The Judgment communication frame does not inherit Judgment because it is not a simple subtype of a purely cognitive state. Judgment communication does not inherit Statement either since it distributes the content of the Statement frame’s Message frame element over two frame elements, Evaluee and Reason.
has super-properties
has frame relationop
has domain
framec
has range
framec
is inverse of
is used byop

Data Properties

annotation set c datedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/annotationSet_cDate

has characteristics: functional

has domain
annotation setc
has range
string

annotation set cxn i ddp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/annotationSet_cxnID

has characteristics: functional

has domain
annotation setc
has range
int

annotation set cxn namedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/annotationSet_cxnName

has characteristics: functional

has domain
annotation setc
has range
string

annotation set i ddp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/annotationSet_ID

has characteristics: functional

has domain
annotation setc
has range
int

annotation set statusdp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/annotationSet_status

has domain
annotation setc
has range
string

corp doc i ddp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/corpDoc_ID

has characteristics: functional

has domain
corp docc
has range
int

corp doc namedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/corpDoc_name

has characteristics: functional

has domain
corp docc
has range
string

definitiondp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/definition

has domain
framec or frame elementc or lex unitc or sem typec
has range
string

document descriptiondp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/document_description

has domain
documentc
has range
string

document i ddp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/document_ID

has characteristics: functional

has domain
documentc
has range
int

f e abbrevdp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/FE_abbrev

has characteristics: functional

has domain
frame elementc
has range
string

f e c bydp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/FE_cBy

has characteristics: functional

has domain
frame elementc
has range
string

f e c datedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/FE_cDate

has characteristics: functional

has domain
frame elementc
has range
string

f e core typedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/FE_coreType

We classify frame elements in terms of how central they are to a particular frame, distinguishing three levels: core, peripheral, and extra-thematic. A fourth possible value for this attribute, called core-unexpressed is also discussed below. A core frame element is one that instantiates a conceptually necessary component of a frame, while making the frame unique and different from other frames. For example, in the Revenge frame, Avenger, Punishment, Offender, Injury, and Injured party are all core frame elements, because an avenging event necessarily includes these participants. One cannot imagine an act of revenge that is not preceded by a (perceived) offense or one that is not directed against anybody. In determining which frame elements are considered core, we also consider some formal properties that provide evidence for core status. These properties are typically co-present, although they need not be. – When an element always has to be overtly specified, it is core. For instance, the verb resemble in the Similarity frame always requires a post-verbal complement NP denoting an entity that is similar to the entity denoted by the subject. – A frame element which, when omitted, receives a definite interpretation, is also core. For instance, when the verb arrive is used only with a Theme-subject, as in John arrived, a particular Goal location that the Theme reaches still has to be understood in the context. Goal, therefore, must be a core frame element. – A frame element whose semantics cannot be predicted from its form, in particular from any marking prepositions, ought to be core since its interpretation completely depends on the target. From this, we can derive two corollaries, given below. -- A frame element that has no formal marking should be core. Thus, frame elements that can be subject or object in a simple active sentence ought to be core since these slots host frame elements of many different kinds and knowing that something is a subject or object is not particularly informative. For example, the Building frame which contains the verb build has at least two core frame elements since the verb build has both a subject and an object. –- A frame element that has idiosyncratic formal marking should also be core. A good example of this is the prepositional verb depend on. The preposition on does not occur as a marker of the same meaning with predicates in many other frames. In its basic spatial sense of ’in contact with and supported by’, on occurs in many different frames; as a marker of Place or Location frame elements it is totally unremarkable and does not suggest core status for these FEs. Frame elements that do not introduce additional, independent or distinct events from the main reported event are characterized as peripheral. Peripheral FEs mark such notions as Time, Place, Manner, Means, Degree, and the like. They do not uniquely characterize a frame, and can be instantiated in any semantically appropriate frame. In respect to the Revenge frame, any report of an event of revenge may also include explicit information about the parameters of time, place, manner, etc. of the revenge, an example of which is given below. (8) The bereaved family retaliated [immediately Time]. Extra-thematic frame elements situate an event against a backdrop of another state of affairs, either of an actual event or state of the same type, as illustrated with Iteration, or by evoking a larger frame within which the reported state of affairs is embedded, as shown for Containing event. (9) Thou shalt not exact revenge [twice Iteration] for the same offense. (10) The Aussies took revenge [in a penalty shootout before 2465 fans in Long Beach the next day Containing event]. Note that extra-thematic frame elements are understood not to conceptually belong to the frames they appear in. We take them to properly be frame elements of other abstract frames that take them as well as the targets that they modify as arguments. Thus, in example (11), we take twice and the verb phrase eat to be arguments of a more abstract Iteration frame. Similarly, in example (12), cooked dinner and me are frame elements of a Benefaction frame. Note that, as shown by (12), the native frame of the extra-thematic frame element need not be evoked by lexical material, it may simply be evoked constructionally. (11) Learn how to spend a few extra minutes planning complementary menus where you cook once and eat [twice]. (12) Lennert, another sweetie in my life, cooked [me] dinner, mmm mmm good. The view of extra-thematic frame elements presented here entails that these frame elements are necessarily the same across all the ‘host’ frames in which they appear. That is, unlike core and peripheral frame elements, extra-thematic frame elements do not have a frame-specific understanding. By comparison, although many core frame elements named Agent share properties with each other due to Inheritance and Using relations, they do not necessarily have identical properties. The value “Core-Unexpressed” is a special notational shorthand. It is assigned to FEs that behave like core frame elements in the frame where they are marked as Core-unexpressed but which, counter to expectation, may not be used for annotation in descendants of that frame. Frame elements marked as core-unexpressed will thus not necessarily be listed among the FEs in descendant frames. We do not consider core-unexpressed frame elements to be violations of our definition of full inheritance. Our reasoning can be illustrated with the example of the core-unexpressed Act frame element in the Intentionally act frame, which is exemplified in (13). (13) I’ll do [the vacuuming Act]. In the many child frames of Intentionally act such as Choosing, Perception active, etc., the idea of an Act is as relevant as in the Intentionally act parent frame. However, in the child frames the frame element is absorbed by the lexical units in the frame and cannot be separately expressed. Marking the frame element Act as core-unexpressed in the Intentionally act parent frame allows us to keep the frames that are lower in the hierarchy from including an inherited FE which for any lexical unit in the frame could at most be annotated on the target itself, but never be expressed separately. The sentence *I chose decision the blue one is simply ungrammatical. Coreness marking makes the most sense for event and state frames, and in these frames we use all three statuses. Coreness marking is done at the level of the frame and is intended to be consistent for all lexical units in a frame. In frames whose LUs are artifacts or natural kinds, we only use a two-way distinction (core and peripheral), noting that the values do not have exactly the same meaning as with events. In such cases, typically there is just one core frame element which is marked on the target word. For instance, in the Clothing frame the FE Clothing is core, and all other FEs are peripheral.

has characteristics: functional

has domain
frame elementc
has range
string

f e i ddp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/FE_ID

has characteristics: functional

has domain
frame elementc
has range
int

f e namedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/FE_name

has characteristics: functional

has domain
frame elementc
has range
string

frame c bydp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/frame_cBy

has characteristics: functional

has domain
framec
has range
string

frame c datedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/frame_cDate

has characteristics: functional

has domain
framec
has range
string

frame i ddp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/frame_ID

has characteristics: functional

has domain
framec
has range
int

frame namedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/frame_name

has characteristics: functional

has domain
framec
has range
string

l u c bydp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/LU_cBy

has characteristics: functional

has domain
lex unitc
has range
string

l u c datedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/LU_cDate

has characteristics: functional

has domain
lex unitc
has range
string

l u i ddp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/LU_ID

has characteristics: functional

has domain
lex unitc
has range
int

l u lemma i ddp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/LU_lemmaID

has characteristics: functional

has domain
lex unitc
has range
int

l u namedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/LU_name

has characteristics: functional

has domain
lex unitc
has range
string

l u p o sdp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/LU_POS

has domain
lex unitc
has range
string

l u statusdp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/LU_status

has domain
lex unitc
has range
string

label c bydp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/label_cBy

has characteristics: functional

has domain
labelc
has range
string

label enddp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/label_end

has domain
labelc
has range
int

label itypedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/label_itype

has domain
labelc
has range
string

label namedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/label_name

has characteristics: functional

has domain
labelc
has range
string

label startdp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/label_start

has domain
labelc
has range
int

layer namedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/layer_name

has characteristics: functional

has domain
layerc
has range
string

layer rankdp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/layer_rank

has domain
layerc
has range
int

lexeme break beforedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/lexeme_breakBefore

has domain
lexemec
has range
boolean

lexeme headworddp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/lexeme_headword

has domain
lexemec
has range
boolean

lexeme namedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/lexeme_name

has characteristics: functional

has domain
lexemec
has range
string

lexeme orderdp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/lexeme_order

has domain
lexemec
has range
int

lexeme p o sdp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/lexeme_POS

has domain
lexemec
has range
string

sem type abbrevdp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/semType_abbrev

has characteristics: functional

has domain
sem typec
has range
string

sem type i ddp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/semType_ID

has characteristics: functional

has domain
sem typec
has range
int

sem type namedp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/semType_name

has characteristics: functional

has domain
sem typec
has range
string

sentence a posdp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/sentence_aPos

has domain
sentencec
has range
string

sentence count annotateddp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/sentenceCount_annotated

has domain
sentence countc
has range
int

sentence count totaldp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/sentenceCount_total

has domain
sentence countc
has range
int

sentence i ddp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/sentence_ID

has characteristics: functional

has domain
sentencec
has range
int

sentence parag nodp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/sentence_paragNo

has domain
sentencec
has range
int

sentence sent nodp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/sentence_sentNo

has domain
sentencec
has range
int

textdp back to ToC or Data Property ToC

IRI: https://w3id.org/framester/framenet/tbox/text

has domain
sentencec
has range
string

Annotation Properties

commentap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2000/01/rdf-schema#comment

creatorap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/creator

labelap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2000/01/rdf-schema#label

version infoap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2002/07/owl#versionInfo

General Axioms

All Disjoint Classes back to ToC

annotation setc, corp docc, documentc, f e core setc, framec, frame elementc, full text annotationc, headerc, labelc, layerc, lex unitc, lexemec, sem typec, sentencec, sentence countc

Namespace Declarations back to ToC

default namespace
https://w3id.org/framester/framenet/tbox/
dc
http://purl.org/dc/elements/1.1/
fn15schema
https://w3id.org/framester/framenet/tbox/
owl
http://www.w3.org/2002/07/owl#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.