Menu
Maps columns in processed tabular data to OWL ontology classes and properties
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | ontology-mapper |
| description | Maps columns in processed tabular data to OWL ontology classes and properties |
| tools | ["run_python_repl"] |
You align tabular data to an OWL ontology by identifying the correct class for each entity and the correct data/object property for each column.
references/owl_primer.md via read_skill_resource("ontology-mapper", "references/owl_primer.md")
to review available OWL classes and properties.mapping = {
"node_type": "Gene", # OWL class name
"id_column": "entrez_id", # column used as IRI
"label_column": "gene_symbol",
"data_property_map": {
"description": "skos:definition",
"chromosome": "faldo:location",
},
}
Note the gap in your response and ask the user whether to add it to the ontology or skip the column for now. Never invent OWL terms that are not in the primer.
Use when evaluating a new biomedical data source (producing a structured report on access method, formats, node/relationship types, and update schedule), or when enabling/disabling sources in config/databases.yaml. Covers the databases.yaml entry format, credential injection via the _env convention, and the checklist for safely enabling a new source. Does not implement parsers or manage ontology mappings.
Use when enforcing OWL ontology terms, adding or modifying OWL classes and object/data properties in the RDF, updating node_types or edge_types in project.yaml, or managing disease scope. Provides scripts/inspect_ontology.py to verify valid names and scripts/edit_ontology.py to add or remove declarations while keeping project.yaml in sync. Owns data/ontology/ontology.rdf and config/project.yaml. Does not manage ontology_mappings.yaml (mapping-protocol's scope) or Python source files.
Use when coordinating across pipeline modules — tracing config ownership (databases.yaml, project.yaml, ontology_mappings.yaml), diagnosing silent failures, or integrating a new data source end-to-end. Covers the six contracts that fail silently (source name consistency, TSV stems, column agreement, node-before-relationship ordering, OWL name validity, credential injection) and the seven-step new-source checklist.
Use when adding, modifying, or fixing entries in config/ontology_mappings.yaml. Maps parser TSV output columns to OWL node types, data properties, and relationship types. Covers config key format, node and relationship entry schemas, the node-before-relationship ordering constraint, merge semantics, filter patterns, skip flag, and pre-flight validation. Requires reading config/project.yaml to confirm valid OWL names before writing entries. Does not modify the OWL RDF file or Python source files.
Use when running, interpreting, or extending the KG build evaluation suite. Covers the three pipeline-stage eval scripts (eval_after_parser.py, eval_after_ontology.py, eval_after_memgraph.py), output JSON format, the three-tier metric system, blocking vs. monitoring thresholds, and adding new metrics. Use when asked to evaluate pipeline output, diagnose zero-count or low-resolution failures, check ontology conformance, run benchmarks, or interpret eval reports.
Use when running the graph export step, inspecting or validating CSV and Cypher outputs, importing the knowledge graph into Memgraph via Docker, or extending MemgraphExporter. Covers running the exporter in isolation, output file formats (nodes_*.csv, edges_*.csv, import.cypher), Docker volume mount, Cypher script validation, and known constraints (string-only values, global node ID uniqueness, graph_indexes is informational).