Morpheme Segmentation in Multi- and Monolingual Wordlists
This package provides implementations for several algorithms by which words in a wordlist can be segmented into morphemes.
If you use this software package, please cite it accordingly:
Rubehn, A. and J.-M. List (2025). MorSeg: A Python package for morpheme segmentation in multi- and monolingual wordlists [Software Library, Version 0.1]. Chair for Multilingual Computational Linguistics, University of Passau.
Installation
This package can be conveniently installed using pip:
pip install morseg
Basic Usage
Loading data
Assuming your data is presented in a TSV file following the LingPy specifications (see /tests/test_data/german.tsv for an example), you can simply load your data with:
from morseg.utils.wrappers import WordlistWrapper
wl = WordlistWrapper.from_file(YOUR_FILE)
This creates a wordlist wrapper object; a representation of a wordlist with three annotation levels: The predicted segmentations (by a model), the Gold standard segmentations, and the unsegmented form. The training of all models requires the data to be stored in this class!
Training a model
The Tokenizer class offers a unified interface for all models that are implemented in this library. For example, if you want to train a LSV (Letter Successor Variety) model, you can simply do so like that:
from morseg.algorithms.tokenizer import LSVTokenizer
model = LSVTokenizer()
model.train(wl)
The current release covers implementations of the following models:
LSVTokenizer: Letter Successor Variety (Harris, 1955) with the following adaptations:- Letter Successor Entropy (Hafer and Weiss, 1974)
- Letter Max-Drop Variety (Hammarström, 2009)
- Normalized Letter Successor Variety (Çöltekin, 2010)
LPVTokenizer: Letter Predecessor Variety (analogically to LSV, but processing the words backwards)LSPVTokenizer: A combination of Letter Successor Variety and Letter Predecessor VarietyMorfessor: The Morfessor Baseline Model (Creutz and Lagus, 2002)SquareEntropyTokenizer(Méndez-Cruz et al., 2016)
Furthermore, some popular models for subword tokenization are implemented:
PairEncoding: Byte-Pair Encoding (Sennrich et al., 2016)WordPiece(Schuster and Nakajima, 2012)UnigramSentencePiece(Kudo, 2018)
Obtain segmentations
You can obtain the predicted segmentations from your training data by calling:
for segmented_word in model.get_segmentations():
# do whatever
You can also try segmenting unseen words (depending on the model, this might work more or less well):
word = ["w", "o", "r", "d"]
segmented_word = model(word)
Metadata
Release files for morseg 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| morseg-0.1.tar.gz | 17.7 kB | Without provenance | Details for morseg-0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| morseg-0.1-py3-none-any.whl | Python 3 | none | any | Details for morseg-0.1-py3-none-any.whl |
Total release size: 34.3 kB
Release files / morseg-0.1.tar.gz
| Download URL | morseg-0.1.tar.gz |
|---|---|
| Size | 17.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2dd394190085c0e384a83d0771c519d31c231e966bfe7ea225e624d74435e1e
|
|
BLAKE2b-256 checksum How to use checksums |
cf518f9567651b27bfe0c6caaf7c341a2c980cbfff1b4defb39b4e41e8e39b36
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.0
|
Release files / morseg-0.1-py3-none-any.whl
| Download URL | morseg-0.1-py3-none-any.whl |
|---|---|
| Size | 16.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ca60f0dcddc56cb156918ab14fde7a81b91177a77507f3f7cfafd7fc937b234c
|
|
BLAKE2b-256 checksum How to use checksums |
db041ace253a2b29cbf01b233bbbe6a6b0eb457bffb860b360823a3dcba509a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.0
|
Security for morseg 0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.