Knowledge graph

Latest stable Based on Graph release 0.5.1

Problem and backend

This example links documents, concepts, and entities so a related result has an explanation path. It uses TinkerGraph to isolate modeling from container and network variance. Read core model and TinkerPop first; use the selection guide before production.

Model

Nodes: Document/Entity/Concept
Edges: MENTIONS/RELATED_TO/IS_A
Key properties: documentId, entityId, conceptId, confidence, relationType

Prerequisites and release boundary

Use JDK 21, commit 3e0fa7cb9e3bc70c2743aeebda2487f3e45e4907, and the checked-in wrapper. Examples are not published; run this release fixture as a Gradle project from the release source checkout. In a consumer application, select only bluetape4k-dependencies:<ecosystem-version> and add the required graph module without an individual version.

Run and observe

./gradlew :knowledge-graph-examples:test --tests "io.bluetape4k.graph.examples.knowledge.TinkerGraphKnowledgeGraphTest"

The tests assert two distinct relations: a document mentions the expected entities, and an entity is classified under the expected concept. A failure usually comes from mention direction, concept classification, or the traversal bound.

Reading order

Continue from code-graph, then read recommendation. Also see paired APIs, testing, and operations.

Exercises and production gaps

Add one result-changing edge and assertion; repeat through the suspend API; then run a persistent-backend concrete test serially. Add disconnected and malformed inputs as diagnostics. This fixture does not prove throughput, clustering, authorization, tenant isolation, migration, backup, remote-driver timeout, or index quality.

Release diagrams

These diagrams are loaded directly from README assets published with the 0.5.1 release and pinned to its immutable commit. They describe this manual’s released structure and runtime flows, not later Snapshot changes. Select a preview to open the SVG at the same release commit.