Skip to content

Repository files navigation

🧠 [[Data]] [[knowledge graph]]

A living [[ontology]] of [[data]] science, ML, and AI built as an Obsidian vault with typed semantic relationships.

Concepts Wikilinks SKOS Coverage Datalog Rules



Not a glossary, a graph. Each concept carries typed relationships in YAML frontmatter (broader, uses, subclass of, …), forming a navigable semantic network. 73 root concepts branch into 8 nesting levels, connected by 7,800+ wikilinks.


📈 Growth

Knowledge Graph Growth

Count
Rich (200+ words) 109
Medium (50–199 words) 112
Stubs (< 50 words) 359
Empty (link targets) 292

🏗️ Structure

Each concept is a markdown file with YAML frontmatter defining typed relationships and wiki-links connecting to related terms:

# Knowledge graph.md
---
uses:
  - "[[Ontology]]"
  - "[[Taxonomy]]"
subclass of:
  - "[[knowledge base]]"
  - "[[labeled directed graph]]"
studied in:
  - "[[Ontology engineering]]"
---
A knowledge graph represents structured domain knowledge
as entities connected by typed relationships...

🗺️ Topics

🤖 AI & LLMs
Agents, RAG, transformers, prompt engineering, LLM evaluation

📊 Machine Learning
Algorithms, training, evaluation metrics, feature engineering

🔧 Data Engineering
Pipelines, data lineage, ETL, data quality

🧬 Deep Learning
Neural networks, CNNs, transformers, attention, backpropagation

🔗 Knowledge Representation
Ontologies, taxonomies, knowledge graphs, SKOS

⚖️ Fairness & Privacy
Bias, FERPA, PII management, interpretability

🏛️ Infrastructure
Cloud, containers, HTTP, authentication, databases

📐 Math & Statistics
Probability, graph theory, vector spaces, combinatorics

💼 Process & Product
Design thinking, CRISP-DM, agile, management


🎯 Use as a Data Ontology

Use case How
GraphRAG Navigate concepts through semantic connections instead of keyword matching
Data catalog enrichment Import as standardized terminology for hierarchical classification
LLM grounding Reduce hallucination through explicit relationship constraints
Onboarding Interactive learning with concept definitions and relationship paths
Metadata schema design Use partOf, uses, subclass of as schema blueprints
Knowledge graph construction Export to Neo4j / RDF by parsing frontmatter into typed edges
Concept disambiguation Canonical definitions that resolve cross-team terminology drift

🔬 Formal Reasoning

scripts/reason.py uses Semantica's Datalog engine for purely logical inference — no LLM involved.

pip install -r requirements.txt

python scripts/reason.py infer          # derived ancestor chains, symmetric related, inverses
python scripts/reason.py check          # cycles, broken links, S27 violations, orphans
python scripts/reason.py query "ancestor(AI agent, ?X)"   # query with real note titles
python scripts/reason.py report         # write stats/reasoning_report.md

9 Datalog rules encode SKOS semantics: transitive broader closure, broadernarrower inverses, related symmetry, cycle detection, and SKOS S27 disjointness.


🌳 Taxonomy — SKOS Broader/Narrower Hierarchy

The graph encodes SKOS-style hierarchical relationships via broader: in YAML frontmatter. 701 of 866 concepts (80.9%) are classified — 73 root concepts, up to 8 nesting levels.

Browse full taxonomy (73 root concepts → 701 classified concepts)

🚀 Getting Started

Explore — Open the graph/ folder in Obsidian and use Graph View to navigate visually.

Export — Convert to other formats:

Target Method
Neo4j Parse frontmatter into Cypher CREATE statements
RDF/OWL Map broader:skos:broader, relationship types → predicates
JSON-LD Export as linked data for web interoperability


Built with Obsidian · Reasoned with Semantica · Stats updated daily via [[GitHub]] Actions

About

Personal Knowledge Graph about Data

Resources

Stars

7 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages