PIBOSO Tagger
This module contains a fully-standalone implementation of the PIBOSO tagger that won the ALTA2012 Shared task [1]. The features and algorithms used are described in [2].
Installing
The tagger (including a pre-trained model) is packaged as a Python module and distributed via pypi. Installing it should be as simple as
pip install piboso
Dependencies
hydrat [3] - automatically installed by pip TreeTagger [4] - must be manually installed
Configuration
The path to the folder in which treetagger is located must be specified in configuration file. When invoked, piboso_tag will attempt to locate a configuration file at ~/.pibosorc and ./.pibosorc. If neither exists, it will generate a blank configuration file at ./.pibosorc. The path to treetagger should be set in this configuration file.
An alternative location for reading the configuration file can be specified with the -c command-line option.
Using the tagger
The tagger can be invoked with the script piboso_tag, that is automatically installed when the package is installed with pip. The simplest invocation is
piboso_tag -o <OUTPUT_PATH> <FILE TO TAG> <FILE TO TAG> …
If no files are specified on the command line, piboso_tag will read STDIN and interpret each line as a path to a file to be tagged. More detailed information about invoking piboso_tag can be obtained by invoking
piboso_tag –help
Files are assumed to be sentence tokenized and presented in a sentence-per-line format. The output produced by piboso-tag is in a CSV format, for example:
subsample/1454068-1,background subsample/1454068-2,background subsample/1454068-3,outcome subsample/1454088-1,background subsample/1454088-2,background subsample/1454088-3,background subsample/1454088-4,background
The first item in each record is the path of the file and the sentence number separated by a dash. Sentences are enumerated from 1. The second item is the label assigned to the sentence.
Contact
Marco Lui <mhlui@unimelb.edu.au>
[1] http://alta.asn.au/events/sharedtask2012/ [2] http://aclweb.org/anthology-new/U/U12/U12-1019.pdf [3] http://hydrat.googlecode.com [4] http://www.ims.uni-stuttgart.de/projekte/corplex/TreeTagger/
1 maintainer
Metadata
1 maintainer
Release files for piboso 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 |
|---|---|---|---|---|
| piboso-1.tar.gz | 24.3 MB | Without provenance | Details for piboso-1.tar.gz |
Release files / piboso-1.tar.gz
| Download URL | piboso-1.tar.gz |
|---|---|
| Size | 24.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c140fe777b25167e7ed1b983f3df1a87508b5d3e2a87c426d393d745d82b9c1f
|
|
BLAKE2b-256 checksum How to use checksums |
658050c408f34d67477d86fffc62dba6ddb499c7d322fafbb2534b5f06139ddc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for piboso 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.
