Skip to content

Jev directory

JevGraph

A schema-guided document-to-graph pipeline: local parsing feeds entity mentions and bounded candidate pairs to Jev, which chooses among closed-set relations, and every edge lands as proposed, review, or rejected with page-level evidence.
Stars
42
Language
Python
License
APACHE-2.0
Reading time
2 min
Published by
Community
Author
chenmingtang830
Last verified
Oct 2026

Highlights

  • Replaces open-ended prompt-to-triples extraction with bounded stages ending in closed-set Jev Choice questions over blocked candidate pairs.
  • On the v0.5.1 FewRel benchmark Jev scored 87.50% planned-case accuracy with 313 ms p50 and 431 ms p95 latency at an illustrative 0.410¢ per 100 decisions.
  • Every edge keeps source and canonical hashes, parser identity, page spans, and character-level evidence offsets; results export as JSON, CSV, or Neo4j Cypher.
  • Quickstart: uv sync --extra documents --extra dev, then uv run jevgraph build with a YAML ontology and entity gazetteer.
  • The authors say the benchmark is one narrow operation, not a general model ranking or an end-to-end knowledge-graph score.

Quickstart

bash
git clone https://github.com/chenmingtang830/jevgraph.git
cd jevgraph
uv sync --extra documents --extra dev

uv run jevgraph build examples/company_events.txt \
  --ontology examples/ontology.yml \
  --entities examples/entities.yml \
  --provider keyword \
  --out runs/demo.json

Watch out

Copy reviewed against the repo README on 2026-10-15. Jev's cost figures are an illustrative list-price equivalent rather than a provider receipt, and the README limits the benchmark to direct relation selection. Output is explicitly not claimed to be true, approved, or safe for consequential reuse.

Questions about this entry

Short answers drawn from the linked project or page.

From the Jev guides

Original write-ups on what this entry is for.

From the Jev AI model community

Posts from builders shipping with Jev right now.

Follow @typesafeai