Semantic Roles and Argument Structure › Frame Semantics

Thematic roles reuse definitions across predicates. A broad inventory can use Goal for both transfer and motion endpoints. Frame semantics defines each role relative to a specific schematic scene.

The contrast is between generality and semantic specificity. Thematic roles aim to be general enough to apply across many predicates. Frame semantics aims to be precise enough to capture the particular structure of each scene. A Goal role can apply to motion and transfer; analyses that treat communication as transfer also use Goal for the recipient (Michaelis and Ruppenhofer, Section 5.3.1). The label alone does not tell us what kind of goal it is. The Recipient role in Giving identifies the receiver in that transfer frame, while a broad Goal role can also cover motion endpoints.

Commercial transactions provide a concrete frame-semantics example. English has several verbs that describe the same scene from different perspectives:

• "The collector bought the painting from the dealer for a thousand dollars."
• "The dealer sold the painting to the collector for a thousand dollars."

The participants are identical: a buyer, a seller, goods, and money. What changes is which participant is foregrounded. Buy takes the buyer's perspective and makes the buyer the subject. Sell takes the seller's perspective. In FrameNet, Commerce_buy and Commerce_sell provide different perspectives on the more neutral Commerce_goods-transfer frame. The Perspective_on relation connects a perspectivized frame to that neutral frame; it is not a direct symmetric link between buying and selling (FrameNet II, Section 6.1.2).

The perspective metaphor is apt. The same scene can be viewed from different angles, and each angle makes a different participant salient. Buy foregrounds the buyer and backgrounds the seller. Sell foregrounds the seller and backgrounds the buyer. The verbs select different perspectives on the transaction; the lexical meaning does not require every participant to be spoken. In the two sentences here, both the goods and the price are explicit.

The Berkeley FrameNet project (Baker, Fillmore, and Lowe, 1998) turned this idea into a lexicon and an annotated corpus. Its core constructs are:

• Frame. A schematic scene such as Giving or Commerce_buy.
• Frame element (FE): a participant role defined by the frame, for example Donor, Theme, and Recipient in Giving. FrameNet II describes three main levels: core (conceptually central), peripheral (background such as Time), and extra-thematic. It also discusses a special core-unexpressed value.
• Lexical unit (LU). A lexical item in one of its senses, paired with the frame it evokes. The item can be multiword. Buy is an LU of Commerce_buy, and sell is an LU of Commerce_sell.
• Frame relations: inheritance, perspective, subframe, and using relations that organize the frame inventory into a network.

The frame-element classification differs from a test of obligatory syntactic expression. A core FE is conceptually central to the frame, but it need not be overt in every sentence. Peripheral FEs provide background such as time or place. Extra-thematic FEs introduce information that can place the target situation within another event or state, such as iteration or a containing event. Consult the particular frame and release: these categories are not interchangeable with PropBank's numbered and AM labels.

FrameNet's role labels are frame-specific. Giving includes Donor, Theme, and Recipient; Commerce_buy includes Buyer, Goods, Seller, and Money. The same participant can therefore receive different labels when a different frame is evoked. When using released data, record the FrameNet version as well as the frame name, since a resource release fixes the definitions and inventories available to the system.

Frame-specific annotation requires consulting the relevant definitions rather than selecting from one short global list. Frame identification and frame-element prediction must agree: a label licensed by one frame may not be licensed by another. A model can share representations across these decisions, but shared features do not make the inventories identical. Annotation time and predictive difficulty depend on the task setup and should be measured rather than inferred from the number of labels alone.

Four lexical resources illustrate different choices about what to organize and annotate.

The table is best read as a map of design tradeoffs rather than a ranking. WordNet organizes lexical senses into synsets and includes syntactic sentence frames for verbs (WordNet Reference Manual, Verb Frames), but it does not provide a PropBank-style role-labeled corpus. VerbNet organizes verbs by syntactic behavior and adds thematic roles and selectional restrictions. PropBank organizes annotations by predicate sense, including verbal and nominal predicates, and uses numbered labels defined by each roleset. FrameNet defines roles for each semantic frame. Each resource answers a different question, and the right choice depends on the task.

VerbNet groups verbs into classes that share syntactic behavior, following Levin's (1993) alternation-based classification. Each class lists its members, the thematic roles its members assign, and the syntactic frames they permit, annotated with semantic predicates that describe event structure, including relevant processes, causes, and states.

VerbNet's great strength is that it links syntax and semantics at the level of verb classes. Class membership gives a system the frames and role definitions recorded for that class. It does not guarantee that a particular release lists every acceptable use of every member. A parser or generator using the lexicon must still select the intended sense and applicable frame.

PropBank (Palmer, Gildea, and Kingsbury, 2005) annotates the Penn Treebank with predicate-argument structure. Its numbered roles A0 through A5 are defined per predicate sense. A0 generally has Proto-Agent properties and A1 generally has Proto-Patient or Theme properties, but these are tendencies rather than substitutes for the frameset. General labels include AM-TMP, AM-LOC, AM-MNR, AM-CAU, and AM-PNC in the older conventions used here. For fear.01, A0 is the experiencer, illustrating why A0 must not be read as a universal volitional-Agent label (frame file).

The phrase "for this particular predicate sense" is the key to understanding PropBank. The numbered labels are not global semantic categories or surface grammatical positions. An annotator consults the sense's role definitions and examples. Some senses do not have an A0 at all: the relevant role inventory must come from the resource, rather than from a rule that assigns A0 to whichever phrase happens to look most agent-like.

FrameNet instead names roles within a frame shared by its lexical units. This provides a different level of organization from a predicate-sense roleset, rather than a general ranking of which resource is better or easier to annotate.

The practical consequence is that role labels from different resources are not interchangeable. For the purchase reading, a PropBank-style task can use numbered labels such as A0 and A1 from buy.01, while a FrameNet task targeting Commerce_buy can use Buyer and Goods. Mappings must specify which senses, frames, and role definitions they align. SemLink distributes explicit mappings between these resources (project description).

The mapping problem is harder than it looks because the resources carve the space differently. PropBank's buy.01 A0 can align to a Buyer role, but the string A0 by itself is insufficient: sell.01 A0 denotes Seller. A mapping must include the selected sense and resource definitions. Existing SemLink mappings are versioned data to inspect, rather than evidence that every label has one universal counterpart.