# graph-annotation

**Repository Path**: mirrors_neo4j-contrib/graph-annotation

## Basic Information

- **Project Name**: graph-annotation
- **Description**: Conventions for annotating a graph, within the graph.
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: main
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2025-11-16
- **Last Updated**: 2026-05-23

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# graph-annotation

Conventions for annotating a graph, within the graph.

Annotations should be useful for:
- graph-level information
- describing labels and properties
- relating labels and properties
- enabling graphs to be self-documenting

This is similar to adding documentation to your source code through structured comments.

## Why? What problem does this solve?

There is often application-level knowledge about a graph that might be useful to others. Sometimes that
knowledge is added to the graph itself. 

For example, the [Knowledge Graph Builder](https://github.com/neo4j-labs/llm-graph-builder) 
creates a graph with some well-known labels:
- `__Entity__` labels for any extracted entity nodes
- `Document` and `Chunk` labels for parts of the lexical graph

Rather than being familiar with that tool's approach, it'd be great if the graph could
explain what labels exist and what they're used for.