Scribd
Upload
55 views2 pages

2.1to3.0. Noun, Verb .Mono

This document describes sense mapping files that map word senses from WordNet version 2.1 to version 3.0 to help users transition between the versions. It provides the file names and formats for the sense mapping files for monosemous and polysemous nouns and verbs. The mappings were determined using heuristics comparing sense keys, synset terms, and tree locations between the versions.

Uploaded by

markrosso
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
55 views2 pages

2.1to3.0. Noun, Verb .Mono

This document describes sense mapping files that map word senses from WordNet version 2.1 to version 3.0 to help users transition between the versions. It provides the file names and formats for the sense mapping files for monosemous and polysemous nouns and verbs. The mappings were determined using heuristics comparing sense keys, synset terms, and tree locations between the versions.

Uploaded by

markrosso
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

WordNet File Formats

SENSEMAP ( 5WN )

NAME

2.1to3.0.noun.poly mapping from polysemous noun senses in WordNet 2.1 to corresponding 3.0
senses
2.1to3.0.noun.mono mapping from monosemous noun senses in WordNet 2.1 to corresponding 3.0
senses
2.1to3.0.verb.poly mapping from polysemous verb senses in WordNet 2.1 to corresponding 3.0 senses
2.1to3.0.verb.poly mapping from monosemous verb senses in WordNet 2.1 to corresponding 3.0
senses
DESCRIPTION

WordNet users who have semantically tagged text to senses in version 2.1, or who have statically
assigned or used 2.1 senses in other applications should upgrade to WordNet 3.0 if possible. To help
users automatically convert 2.1 noun and verb senses to their corresponding 3.0 senses, we provide sense
mapping information with version 3.0.
The sense mapping was done as follows:

Nouns and verbs unique to either database were ignored.

Nouns and verbs that are monosemous in both databases were found and their sense_keys
and synset_offsets were mapped. These sense mappings are in the files
2.1to3.0.{noun,verb}.mono.

All senses of polysemous nouns and verb in version 2.1 were mapped to senses in version
3.0. Various heuristics were used to evaluate the similarity of 2.1 and 3.0 senses, and a
score was assigned to each comparison. For each word, each 2.1 sense was compared to
all of the 3.0 senses for the same word, and the 3.0 sense (or senses) with the highest
score was deemed the best mapping. These sense mappings are in the file
2.1to3.0.{noun,verb}.poly.
Heuristics include comparison of sense keys, similarity of synset terms, and relative tree
location (comparision of hypernyms). Glosses are not used for comparisions, as they are
often significantly modified.

File Format

A sense mapping is generally represented by two sense_key synset_offset pairs, one for the 2.1 sense
and one for its corresponding 3.0 sense. For the polysemous sense mappings, sense_number is also in
each pair. This field is not needed in the monosemous mappings since all monosemous words are
assigned sense_number 1. See senseidx(5WN) for a detailed description of these fields.
In all the mapping files, a space is the field delimiter unless otherwise noted, and each line is terminated
with a newline character.
2.1to3.0.{noun,verb}.mono

These files contain the mapping of sense keys for nouns and verbs that are monosemous in both WordNet 2.1 and 3.0. Although the actual words and sense numbers are the same in both databases, not all
sense_keys are the same, and the synset_offsets are different. This file is an alphabetized list of one
mapping per line. Each line is of the form:
2.1_sense_key;2.1_synset_offset 3.0_sense_key;3.0_synset_offset
2.1to3.0.{noun,verb}.poly

These files contain the mapping of sense keys for nouns and verbs that are polysemous in WordNet 2.1
and are also found in 3.0. This file is sorted by score from highest score (100) to lowest (0), and then
alphabetically within each score. Each line lists all 3.0 sense(s) that the corresponding 2.1 sense maps

WordNet 3.0

Last change: February 2007

WordNet File Formats

SENSEMAP ( 5WN )

to with that score. Each line is of the form:


score 2.1_sense_info 3.0_sense_info [3.0_sense_info...]
where sense_info consists of the following three fields:
sense_key;synset_offset;sense_number
SCORES

Scores range from 0 to 100, and are an indication of how confident the mapping heuristics are that the
senses are the same a higher score indicates greater reliability in the mapping. The vast majority of
senses mapped with a score of 90 or 100.
NOTES

The number of senses of a polysemous word in version 2.1 often differs from the number of senses for
the same word in version 3.0. While there will always be a mapping for each 2.1 sense to one or more
3.0 senses, there may be 3.0 senses to which no 2.1 sense is mapped.
WordNet 2.1 words not found in either of the monsemous maps are unique to version 2.1, and therefore
cannot be mapped to version 3.0.
ENVIRONMENT VARIABLES

WNHOME

Base directory for WordNet. Unix default is /usr/local/WordNet-3.0, Windows


default is C:\Program Files\WordNet\3.0.

FILES

All files are in WNHOME/sensemap on Unix platforms, WNHOME\sensemap on Windows.


FILES

2.1to3.0.noun.poly

mapping of polysemous 2.1 noun senses to 3.0 senses

2.1to3.0.verb.poly

mapping of polysemous 2.1 verb senses to 3.0 senses

2.1to3.0.noun.mono

mapping of monosemous 2.1 noun senses to 3.0 senses

2.1to3.0.verb.mono

mapping of monosemous 2.1 verb senses to 3.0 senses

SEE ALSO

senseidx(5WN), wndb(5WN), wnpkgs(7WN).

WordNet 3.0

Last change: February 2007

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy