Tablassert
Extract knowledge assertions from tabular data into NCATS Translator-compliant KGX NDJSON, declaratively, with entity resolution built in and optional quality control.
Tablassert turns biomedical spreadsheets (Excel, CSV, TSV) into knowledge graphs ready for NCATS Translator. Declare how your columns map to subject-predicate-object statements in YAML; Tablassert resolves free text to standard CURIEs, attaches provenance and statistical annotations, and emits KGX-compliant nodes and edges.
Full Documentation: installation guides, tutorial, configuration reference, and API docs.
Statement of need
Biomedical knowledge lives in spreadsheets: association tables, assay results, curated gene-disease lists. Getting those rows into an NCATS Translator knowledge graph means writing an ingest that maps columns to Biolink statements, resolves free text ("TP53", "lung cancer") to standard CURIEs, and records provenance, terms of use, and statistical annotations. Today that ingest is Python code maintained per source, and entity resolution usually means calling a hosted name-resolution service at build time.
Tablassert replaces the per-source code with a declarative YAML mapping plus an embedded, offline
entity-resolution database built from RENCI BABEL exports, so a build is reproducible, auditable,
and network-free. It is aimed at Translator ingest authors and knowledge-graph data engineers who
hold tabular biomedical sources, and at bioinformatics groups that want a validated KGX output
without writing a transform pipeline. The configuration model and the Biolink/KGX contracts it
emits follow current NCATSTranslator/translator-ingests
practice, and each build can emit the Resource Ingest Guide (RIG) metadata those submissions require.
Getting help
- Questions and bug reports: open an issue at
github.com/SkyeAv/Tablassert/issues (use the
questionlabel for usage questions). Include the command you ran, its output, and yourtablassert --version. - Contributing code or docs: see CONTRIBUTING.md for setup, the local quality gates, and pull-request expectations. By participating in this project you agree to follow the Code of Conduct.
- Reference: the CLI Reference and configuration guides document every flag and field.
Quick Start
pip install "tablassert[cli]"
Given a CSV of gene-disease associations with p-values and sample sizes, declare the mapping in a
table config (table.yaml):
template:
source:
kind: text
local: ./gene-disease.csv
url: [https://example.com/data.csv]
row_slice: [1, auto]
delimiter: ","
statement:
subject: { method: column, encoding: A, prioritize: [Gene] }
predicate: associated_with
object: { method: column, encoding: B, prioritize: [Disease] }
provenance: { repo: PMID, publication: "12345678" }
annotations:
- { annotation: p_value, method: column, encoding: C }
- { annotation: study_size, method: column, encoding: D }
Wrap it in a graph config (graph.yaml) pointing at your fullmap entity-resolution database
and carrying the required rig: metadata for the generated Resource Ingest Guide. Build or
download that database once first (tablassert build-fullmap, a multi-GB download; see the
Fullmap guide), which makes ./fullmap below the
right path:
name: MY_KG
version: 1.0.0
tables:
- ./table.yaml
fullmap: ./fullmap
rig:
source_info:
infores_id: infores:my-kg
terms_of_use_info:
terms_of_use_url: https://example.org/terms
data_access_locations:
- My source downloads - https://example.org/downloads
source_status: maintained_regular_updates
ingest_info:
utility: Gene-disease associations support Translator disease-mechanism queries.
scope: Gene-disease associations extracted from tabular sources.
provenance_info:
contributions:
- "Author Name - code author, data modeling"
artifact_base_url: https://example.org/my-kg
artifact_base_path: ./published/my-kg
Build the knowledge graph:
tablassert build-kg graph.yaml
Output is one JSON object per line: nodes with Biolink categories, edges with annotations. The edge sample below is abridged; real records also carry provenance fields such as knowledge_level, agent_type, sources, and original_subject/original_object.
{"id":"HGNC:11998","name":"TP53","category":["biolink:Gene"],"in_taxon":["NCBITaxon:9606"],"provided_by":["infores:my-kg"]}
{"id":"MONDO:0008903","name":"lung cancer","category":["biolink:Disease"],"in_taxon":["NCBITaxon:9606"],"provided_by":["infores:my-kg"]}
{"id":"8f41c2d7-9b3e-35c1-a4e8-6d2f9a0c5b71","subject":"HGNC:11998","predicate":"biolink:associated_with","object":"MONDO:0008903","p_value":"1.0000e-03","statistical_significance_qualifier":"very_strongly_significant","has_supporting_studies":{"PMID:12345678":{"id":"PMID:12345678","name":"gene-disease.yaml SECTION 1","study_size":450,"has_study_results":[{"id":"row:2"}]}},"publications":["PMID:12345678"]}
See the Tutorial for the full walkthrough.
Key Features
- Declarative YAML configuration: define data transformations without writing code
- Built-in entity resolution: map free text to genes, diseases, and chemicals with standard CURIEs, taxonomic filtering, and provenance, backed by an embedded redb database
- Optional quality control: a four-stage audit (exact match, fuzzy match, abbreviation expansion, then SapBERT embeddings) flags low-confidence mappings
- KGX compliance: emits NCATS Translator-compatible node/edge NDJSON with Biolink categories and predicates
- Performance & reproducibility: lazy Polars pipelines and a deterministic UV-based development environment
Installation
pip install tablassert
To use the Python API, install Tablassert into your project's environment with pip install "tablassert" (or uv add tablassert). To get the tablassert command as a standalone tool, use
uv tool install "tablassert[cli]"; note that a tool install is isolated and does not expose the
Python API to your project. Other extras are opt-in:
| Extra | Adds | Install |
|---|---|---|
cli |
tablassert command and rich terminal progress |
pip install "tablassert[cli]" |
rt |
CPU-compatible Polars runtime | pip install "tablassert[rt]" |
aria2 |
bundled aria2c downloader, used automatically by build-fullmap when installed (Linux/Windows wheels only) |
pip install "tablassert[aria2]" |
qc |
four-stage QC audit (exact match, fuzzy match, abbreviation expansion, and SapBERT embeddings) | pip install "tablassert[qc]" |
log |
loguru-backed file/progress logging (rotation, enqueue) | pip install "tablassert[log]" |
Reaching a feature whose extra is missing never produces a bare ModuleNotFoundError: the failure
names the missing package and the install command that fixes it. QC is opt-in at build time
(build-kg --qc). See the
Installation guide for the full matrix,
per-command preflight behavior, and the
CLI Reference for every flag.
Entity Resolution API
from pathlib import Path
from tablassert.lib import resolve_many
results = resolve_many(
col="gene",
entities=["TP53", "BRCA1"],
fullmap=Path("/path/to/fullmap"),
taxon="9606",
)
# [{"original_gene": "TP53", "gene": "HGNC:11998", "gene_name": "TP53", ...}, ...]
Point resolve_many() at a fullmap database to resolve any iterable of entity strings to CURIEs,
no LazyFrame setup or NLP preprocessing required. See the
Batch Resolution API for the full reference.
Documentation
- Installation: install methods, extras, and development setup
- Tutorial: step-by-step example with synthetic data
- Use Case Gallery: real-world configuration patterns
- CLI Reference: complete command-line flag reference
- Fullmap: building and querying the entity-resolution database
- Configuration: graph and table configuration reference
- API Reference: core functions documentation
- Development: dev environment setup and contributor workflow
- Changelog: release history
Developing
uv sync --group dev --extra cli --extra qc --extra log
uv run maturin develop --manifest-path rust/Cargo.toml
make check
See CONTRIBUTING.md for the full development loop, quality gates, and pull request guidelines.
Citation
If you use Tablassert, please cite it as described in CITATION.cff. The approach is described in:
Skye Lane Goetz, Amy K. Glen, and Gwênlyn Glusman. "MicrobiomeKG: bridging microbiome research and host health through knowledge graphs." Frontiers in Systems Biology 5 (2025). doi:10.3389/fsysb.2025.1544432
License
Contributors
- Skye Lane Goetz, Institute for Systems Biology
- Gwênlyn Glusman, Institute for Systems Biology
- Jared C. Roach, Institute for Systems Biology
1 maintainer
Metadata
1 maintainer
Release files for tablassert 22.2.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 | |
|---|---|---|---|---|
| tablassert-22.2.0.tar.gz | 372.9 kB | With provenance | Details |
Built distributions (wheels)
Total release size: 15.5 MB
Release files / tablassert-22.2.0.tar.gz
| Download URL | tablassert-22.2.0.tar.gz |
|---|---|
| Size | 372.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8778eb9e46f2b37ea96cec15906c894de5e38e5c657ec48f5f82b60d519be367
|
|
BLAKE2b-256 checksum How to use checksums |
b37ef6a3ae044f4ac8919d3ee240ec416a391040916ba83a360f65b5b4a1467c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.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.
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 Oct 22, 2026.
Transparency logRelease files / tablassert-22.2.0-cp315-cp315-macosx_11_0_arm64.whl
| Download URL | tablassert-22.2.0-cp315-cp315-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.15 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
96097dd102c1bc7ac480c185210754a930f7d5b4d8b354d7d65bf2d99c68bacd
|
|
BLAKE2b-256 checksum How to use checksums |
1e4eefa047378ffa42ae0163c277681797246d5ab6c00e11c1716f21764b1cfd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.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.
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 Oct 22, 2026.
Transparency logRelease files / tablassert-22.2.0-cp314-cp314-manylinux_2_34_x86_64.whl
| Download URL | tablassert-22.2.0-cp314-cp314-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.14 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
d5c8a2b3d254b38d5ff49904fc02e6a2a7dce5a3f1281045f9b76b20794b5a22
|
|
BLAKE2b-256 checksum How to use checksums |
b62b3d38e377cff33c93aadd80eeef6cdf44085dfc681395dc4f7541edf656bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.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.
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 Oct 22, 2026.
Transparency logRelease files / tablassert-22.2.0-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | tablassert-22.2.0-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b777beb730ebc0d536fc13f01f1ac09c2e33077144238a4bfd3eb326976d127f
|
|
BLAKE2b-256 checksum How to use checksums |
2e255625161af14aa6c42c8daf1f3fab87aa2d6b159afb05e967cf132e1bdb68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.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.
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 Oct 22, 2026.
Transparency logRelease files / tablassert-22.2.0-cp313-cp313-manylinux_2_34_x86_64.whl
| Download URL | tablassert-22.2.0-cp313-cp313-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.13 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
0dcbfc763d6bc1248c4869fcaf5ee00f4d9265e99f6ad77328ee84bf11bddef0
|
|
BLAKE2b-256 checksum How to use checksums |
d3261ca9dda780ffe283ab790789ff9ce163a5211953d3356e4e75e633946591
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.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.
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 Oct 22, 2026.
Transparency logRelease files / tablassert-22.2.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | tablassert-22.2.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d86c68ba103feab73f7b1880e46059b169a53466cc8fbd7b4d1189c9da7d207e
|
|
BLAKE2b-256 checksum How to use checksums |
00a14ad16d916b7fa7d97c52dbc0ecf8c14bae868362ab3b2dba4fbfff738f83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.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.
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 Oct 22, 2026.
Transparency logRelease files / tablassert-22.2.0-cp312-cp312-manylinux_2_34_x86_64.whl
| Download URL | tablassert-22.2.0-cp312-cp312-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.12 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
186225365723e084fadeec8628c3007d7d9d773ed3315ecfc24784468bfd7a25
|
|
BLAKE2b-256 checksum How to use checksums |
f1b83e1bef19649632d24ff2eb9612c03025a1a7b315b157730bf5bf10da3c1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.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.
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 Oct 22, 2026.
Transparency logRelease files / tablassert-22.2.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | tablassert-22.2.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
ba3dab5093a953e05d5c5676ef205b66136c56ad45adf699503f80cd4f13701a
|
|
BLAKE2b-256 checksum How to use checksums |
7b469e0f619512f57a7bb3bac11da061c88f25a0917303764cbd17394ead15c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.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.
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 Oct 22, 2026.
Transparency logRelease files / tablassert-22.2.0-cp311-cp311-manylinux_2_34_x86_64.whl
| Download URL | tablassert-22.2.0-cp311-cp311-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.11 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
96f48d3d861c630c6a9ba75f319dcdd1a478afd3e94b84e80ffcb960f31331ea
|
|
BLAKE2b-256 checksum How to use checksums |
e189f039fda4fec3098982c8738bd9060fd1a87f2cb7bb5fe8394c2e325ba453
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.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.
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 Oct 22, 2026.
Transparency logRelease files / tablassert-22.2.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | tablassert-22.2.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
e33e8b7b32f967bb77f3d7db4ce84adad1b5bf4db80297de0e2c0e5553e6077f
|
|
BLAKE2b-256 checksum How to use checksums |
5916d6577c050b0ab87baf6262b70d61013d95cf91f4b36285d08cd239fd0d94
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.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.
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 Oct 22, 2026.
Transparency logSecurity for tablassert 22.2.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 10 files in this release have been uploaded with provenance metadata.
Attestation for tablassert-22.2.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 Oct 22, 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.
