PropBank (2005) › The Solution: Numbered Arguments and Frame Files

PropBank addressed this problem by creating a semantic annotation layer that worked directly with the existing Penn Treebank syntactic trees. The solution had two key components: numbered arguments that could scale across different verbs, and verb-specific frame files that defined what each numbered argument represented for particular verbs. This design enabled PropBank to provide broader coverage than FrameNet while maintaining compatibility with the most widely used syntactic resource in computational linguistics.

PropBank's core innovation was using numbered arguments (Arg0, Arg1, Arg2, etc.) rather than named semantic roles. For verbs, these arguments had general semantic interpretations:

• Arg0: Typically the agent or proto-agent (the entity that performs the action)
• Arg1: Typically the patient, theme, or proto-patient (the entity affected by the action)
• Arg2: Typically the beneficiary, recipient, or instrument
• Arg3: Often the start point, benefactive, or attribute
• Arg4: Often the end point

These general interpretations provided consistency across verbs, while verb-specific frame files defined what each numbered argument meant for a particular verb. For "give," the frame file might specify that Arg0 is the giver, Arg1 is what is given, and Arg2 is the recipient. For "buy," Arg0 would be the buyer, Arg1 what is bought, and Arg2 the seller or source. The general numbering supported reuse, while the frame files preserved verb-specific distinctions.

The numbered argument scheme had several advantages. It was simpler to annotate than creating detailed named frames, enabling faster annotation and broader coverage. It was compatible with the Penn Treebank's tree structures, allowing annotators to mark semantic roles directly on existing syntactic nodes. It provided a framework that machine learning systems could learn from, with consistent argument numbering patterns across verbs. And it allowed verb-specific distinctions through frame files, avoiding the one-size-fits-all problem that purely general schemes might face.

Each verb in PropBank was associated with a frame file that defined the possible semantic roles for that verb. These frame files specified what each numbered argument (Arg0, Arg1, Arg2, etc.) represented for that particular verb. This ensured consistency in annotation across different occurrences of the same verb. Frame files also documented the syntactic realizations typical for each argument, such as whether Arg0 typically appears as the subject or whether Arg2 typically appears with a preposition.

Consider the verb "break." Its frame file might specify that Arg0 is the agent that causes the breaking (typically the subject), Arg1 is what gets broken (typically the object), and Arg2 might be the instrument used (typically a prepositional phrase with "with"). The frame file captures both the semantic roles and their typical syntactic realizations. This provided a complete picture of how this verb structures events. When annotators encountered "John broke the window with a hammer," they could consistently mark John as Arg0 (the agent), "the window" as Arg1 (what was broken), and "a hammer" as Arg2 (the instrument).

Frame files also handled verb alternations, where the same verb can appear in different syntactic frames while maintaining similar semantics. The verb "load" can appear as "John loaded the truck with boxes" (where Arg0 is the agent, Arg1 is the location, and Arg2 is what is loaded) or "John loaded boxes onto the truck" (where Arg0 is the agent, Arg1 is what is loaded, and Arg2 is the location). The frame file documents both patterns, showing how the same verb can realize its arguments differently while maintaining consistent semantic roles.

The PropBank annotation process involved several systematic steps. First, annotators identified the main predicate of each sentence, typically a verb. Then, they consulted the frame file for that verb to determine what semantic roles were possible. Next, they identified the arguments of the predicate in the Penn Treebank tree and determined which numbered arguments they represented based on the frame file. The annotation also included information about the syntactic realization of each argument, such as whether it was a noun phrase, prepositional phrase, or other syntactic category.

This dual annotation of semantic roles and syntactic realization made PropBank useful for both semantic and syntactic analysis. Systems could use the semantic role labels directly for semantic understanding tasks, or they could study the relationship between syntax and semantics by examining how semantic roles were realized syntactically. This combination proved valuable for research on argument alternations, voice constructions, and other phenomena where syntactic and semantic structures interact.

The annotation scheme was designed for the existing Penn Treebank trees. Semantic roles were marked on the same structures as the syntactic annotations, so researchers could use both levels in one analysis rather than maintain separate corpora.

PropBank's simpler annotation scheme enabled broader coverage than FrameNet. By 2010, PropBank had annotated over 1 million words of text with semantic roles, covering substantially more lexical units than FrameNet's detailed frame annotations. This broader coverage made PropBank more useful for applications that needed to process unrestricted text, where encountering unannotated lexical units was common. The resource became the standard for semantic role labeling tasks precisely because of this coverage advantage.

The coverage advantage came from PropBank's efficient annotation process. Rather than creating detailed frame definitions for each lexical unit, annotators could use the general numbered argument scheme with verb-specific frame files. This process was faster than FrameNet's frame creation, enabling PropBank to annotate more text in less time. The trade-off was less detailed semantic structures than FrameNet provided, but for many applications, the broader coverage was more valuable than the additional detail.