negspacy: negation for spaCy
spaCy pipeline object for negating concepts in text. Based on the NegEx algorithm.
NegEx - A Simple Algorithm for Identifying Negated Findings and Diseases in Discharge Summaries Chapman, Bridewell, Hanbury, Cooper, Buchanan https://doi.org/10.1006/jbin.2001.1029
What's new
Version 1.0 is a major version update providing support for spaCy 3.0's new interface for adding pipeline components. As a result, it is not backwards compatible with previous versions of negspacy.
If your project uses spaCy 2.3.5 or earlier, you will need to use version 0.1.9. See archived readme.
Installation and usage
Install the library.
pip install negspacy
Import library and spaCy.
import spacy
from negspacy.negation import Negex
Load spacy language model. Add negspacy pipeline object. Filtering on entity types is optional.
nlp = spacy.load("en_core_web_sm")
nlp.add_pipe("negex", config={"ent_types":["PERSON","ORG"]})
View negations.
doc = nlp("She does not like Steve Jobs but likes Apple products.")
for e in doc.ents:
print(e.text, e._.negex)
Steve Jobs True
Apple False
Consider pairing with scispacy to find UMLS concepts in text and process negations.
NegEx Patterns
- pseudo_negations - phrases that are false triggers, ambiguous negations, or double negatives
- preceding_negations - negation phrases that precede an entity
- following_negations - negation phrases that follow an entity
- termination - phrases that cut a sentence in parts, for purposes of negation detection (.e.g., "but")
Termsets
Designate termset to use, en_clinical is used by default.
en= phrases for general english language texten_clinicalDEFAULT = adds phrases specific to clinical domain to general englishen_clinical_sensitive= adds additional phrases to help rule out historical and possibly irrelevant entities
To set:
from negspacy.negation import Negex
from negspacy.termsets import termset
ts = termset("en")
nlp = spacy.load("en_core_web_sm")
nlp.add_pipe(
"negex",
config={
"neg_termset":ts.get_patterns()
}
)
Additional Functionality
Change patterns or view patterns in use
Replace all patterns with your own set
nlp = spacy.load("en_core_web_sm")
nlp.add_pipe(
"negex",
config={
"neg_termset":{
"pseudo_negations": ["might not"],
"preceding_negations": ["not"],
"following_negations":["declined"],
"termination": ["but","however"]
}
}
)
Add and remove individual patterns on the fly from built-in termsets
from negspacy.termsets import termset
ts = termset("en")
ts.add_patterns({
"pseudo_negations": ["my favorite pattern"],
"termination": ["these are", "great patterns", "but"],
"preceding_negations": ["wow a negation"],
"following_negations": ["extra negation"],
})
#OR
ts.remove_patterns(
{
"termination": ["these are", "great patterns"],
"pseudo_negations": ["my favorite pattern"],
"preceding_negations": ["denied", "wow a negation"],
"following_negations": ["unlikely", "extra negation"],
}
)
View patterns in use
from negspacy.termsets import termset
ts = termset("en_clinical")
print(ts.get_patterns())
Negations with Spans
Span Groups can be negated by providing a list of span keys to the span_keys argument.
Load spacy language model that adds spans to the Doc object.
nlp = spacy.load("your_span_cat_model")
# 'sc' is the default SpanGroup spans_key
nlp.add_pipe("negex", config={"span_keys":["sc"]})
View negations.
doc = nlp("Analysis showed no sign of Human TR Beta 1 mRNA")
for span in doc.spans["sc"]:
print(span.text, span.label, span._.negex)
Human TR Beta 1 PROTEIN True
Human TR Beta 1 mRNA RNA True
Negations in noun chunks
Depending on the Named Entity Recognition model you are using, you may have negations "chunked together" with nouns. For example:
nlp = spacy.load("en_core_sci_sm")
doc = nlp("There is no headache.")
for e in doc.ents:
print(e.text)
# no headache
This would cause the Negex algorithm to miss the preceding negation. To account for this, you can add a chunk_prefix:
nlp = spacy.load("en_core_sci_sm")
ts = termset("en_clinical")
nlp.add_pipe(
"negex",
config={
"chunk_prefix": ["no"],
},
last=True,
)
doc = nlp("There is no headache.")
for e in doc.ents:
print(e.text, e._.negex)
# no headache True
Contributing
Authors
- Jeno Pizarro
License
Other libraries
This library is featured in the spaCy Universe. Check it out for other useful libraries and inspiration.
If you're looking for a spaCy pipeline object to extract values that correspond to a named entity (e.g., birth dates, account numbers, or laboratory results) take a look at extractacy.
Metadata
Release files for negspacy 1.1.0
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 |
|---|---|---|---|---|
| negspacy-1.1.0.tar.gz | 40.1 kB | With provenance | Details for negspacy-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| negspacy-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for negspacy-1.1.0-py3-none-any.whl |
Total release size: 50.8 kB
Release files / negspacy-1.1.0.tar.gz
| Download URL | negspacy-1.1.0.tar.gz |
|---|---|
| Size | 40.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13d8c4d7bd1b9f5c7e83bc1d7e4689ca70ace3232b8b0c38c22a3807fc0b9a1f
|
|
BLAKE2b-256 checksum How to use checksums |
7ce47207fe5ad3d9a67bf0313db555fe7ea043d101ae33af2e39a70028970c65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 20, 2026.
Transparency logRelease files / negspacy-1.1.0-py3-none-any.whl
| Download URL | negspacy-1.1.0-py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52b88bf1e842fbcd02c5a3ef594daf4149b8737f6237f01436a2f8b95c16d6b2
|
|
BLAKE2b-256 checksum How to use checksums |
4c0d6d8ff299e43ae1c014fe1a8c5e258dcf603c5e0d8ef309a4d6e5f0d1fc54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 20, 2026.
Transparency logSecurity for negspacy 1.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for negspacy-1.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 20, 2026.
Transparency logA 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.