PyTrips 
PyTrips provides a python interface to interacting with the TRIPS ontology and parser.
Installation
pip install pytrips
pip install pytrips[tools] # optional
python -c "import nltk; nltk.download('wordnet')"
Basic Usage
Load the ontology and retrieve a type by name:
from pytrips.ontology import load
ont = load()
catch = ont["catch"] # lookup an ontology type
And then inspect said type:
print(catch)
print(catch.parent)
print(catch.children)
print(catch.arguments)
which should result in:
# ont::catch
# ont::co-motion
# []
# [<TripsRestriction :neutral >, <TripsRestriction :source >, <TripsRestriction :result >, <TripsRestriction :extent >, <TripsRestriction :affected >, <TripsRestriction :agent >]
Check if types subsume each other:
catch < ont["event-of-action"]
# Make sure at least one type is explicitly a TripsType. The other can be a string.
"food" > ont["bread"]
Or get the lowest common subsumer of two types:
ont["bread"] ^ ont["geo-object"]
For simplicity, lookup words and ontology types in the same way:
ont["person"] # default is to look up an ontology type
ont["ont::person"] # explicitly get the ontology type named "ont::person"
ont["w::person"] # or lookup the list of ontology types that the word "person" can map to
WordNet lookups are similar:
ont["wn::cat%1:06:00::"]
>> [ont::device]
ont["q::cat"] # returns all lexical and wordnet mappings for the word cat in a dictionary
>> {'lex': [ont::nonhuman-animal, ont::medical-diagnostic],
'wn': [ont::pharmacologic-substance,
ont::female-person,
ont::communication-party,
ont::male-person,
ont::medication,
ont::mammal,
ont::device,
ont::land-vehicle,
ont::vomit]}
Or we can specify a part of speech to limit the search:
ont[("q::move", 'v')]
>> {'lex': [ont::cause-move, ont::move, ont::provoke, ont::activity-ongoing],
'wn': [ont::cause-effect,
ont::change,
ont::believe,
ont::activity-event,
ont::commerce-sell,
ont::move,
ont::progress,
ont::live,
ont::suggest]}
1 maintainer
Metadata
1 maintainer
Release files for pytrips 0.5.16
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 | |
|---|---|---|---|---|
| pytrips-0.5.16.tar.gz | 14.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytrips-0.5.16-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.9 kB
Release files / pytrips-0.5.16.tar.gz
| Download URL | pytrips-0.5.16.tar.gz |
|---|---|
| Size | 14.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
decaa55058ce0bd5eb06fb1e69c1798629ef8b57fb33ef3d65c9ec98dedccb4b
|
|
BLAKE2b-256 checksum How to use checksums |
68e882d1d8e81f97756a43c423bb8b0f788cd663372e7e86d322f3c0b7ec8bbc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.35.0 CPython/3.7.3
|
Release files / pytrips-0.5.16-py3-none-any.whl
| Download URL | pytrips-0.5.16-py3-none-any.whl |
|---|---|
| Size | 25.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a9f31a8705bff527d295baf8fb058bd909b20c151e2b1cd1229d0c750f6e4a57
|
|
BLAKE2b-256 checksum How to use checksums |
f731e8d98dcba3dc13388bbe01154eb8d8d6d0084862316f730a453382797f0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.35.0 CPython/3.7.3
|
Security for pytrips 0.5.16
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.
