kraph
The python client for kraph, the Arkitekt knowledge graph service built around Apache AGE: recording claims about entities, events, measurements and metrics, backed by the structures (images, tables, …) that are evidence for them, and drawing them into graphs.
Installation
pip install kraph
With arkitekt, pip install "arkitekt[rekuest,kraph]" brings it in.
Concepts
- Claims — an entity exists, a structure measures it, two things are related — are recorded under a term, a word your organization owns, never under a graph. Retracting a claim records a position rather than deleting anything.
- Graphs are views. A graph declares categories (entity, relation, measurement, event, …) that say what its words mean, and draws the claims made under those words.
Usage
Every kraph operation is a method of the Kraph client, in a blocking and an a-prefixed async
flavour (kraph.create_graph(...), await kraph.acreate_graph(...)). What a call returns remembers
the client, so follow-ups from a result go through the same client.
In an arkitekt app
Add the service to your app and ask for kraph: Kraph; the client is injected by annotation.
Graphs, categories, structures, metrics, terms and more travel between actions by id
(@kraph/graph, @kraph/entitycategory, @kraph/structure, @kraph/term, …), so an action can
take and return them directly:
from arkitekt import App, run
from kraph import Kraph, kraph_service
app = App("neuron-claims", "0.1.0", services=[kraph_service])
@app.action
def claim_neuron(kraph: Kraph) -> str:
"""Claim Neuron
Records that a neuron exists.
"""
asserted = kraph.assert_entity_exists(
term="Neuron", supporting_evidence=[], derived_from=[], same_as=[]
)
return asserted.instance.id
if __name__ == "__main__":
run(app)
From a script
from arkitekt import easy
from kraph import kraph_service
with easy("my-script", kraph_service) as kraph:
graph = kraph.create_graph(name="Neurons", backfill=False)
kraph.create_entity_category(
key="Neuron",
ontology_references=[],
property_definitions=[],
graph=graph.id,
backfill=True,
)
asserted = kraph.assert_entity_exists(
term="Neuron", supporting_evidence=[], derived_from=[], same_as=[]
)
print(asserted.is_drawn) # True: the graph declares "Neuron", so it draws the claim
Testing
uv run pytest -m "not integration" # no server needed
uv run pytest -m integration # a real kraph via dokker
See RELEASING.md for how versions are cut.
1 maintainer
Metadata
1 maintainer
Release files for kraph 5.0.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 | |
|---|---|---|---|---|
| kraph-5.0.0.tar.gz | 110.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kraph-5.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 225.1 kB
Release files / kraph-5.0.0.tar.gz
| Download URL | kraph-5.0.0.tar.gz |
|---|---|
| Size | 110.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f10367b4d78227577559b1f06af0f33fd86e72fa4d10fd24df2b6f40ef4436dd
|
|
BLAKE2b-256 checksum How to use checksums |
e2d4801f51debe4bfdba7a207ac9df60f964b22d2ef8b37283ae3c00f30a7192
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.3 {"installer":{"name":"uv","version":"0.13.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / kraph-5.0.0-py3-none-any.whl
| Download URL | kraph-5.0.0-py3-none-any.whl |
|---|---|
| Size | 115.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
299058188779efcecb80a63058e258774a5bda3a21e7102e2360c2e9434f23e4
|
|
BLAKE2b-256 checksum How to use checksums |
a5977dbf8a335c8854f0d3efbf72ecac1c76aa7aa0655f4651806e0a5cd3fa8a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.3 {"installer":{"name":"uv","version":"0.13.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for kraph 5.0.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.
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.
