Ontology Refinement
Iteratively improve the ontology. Merge near-duplicates, fill identified gaps, update confidence scores based on new evidence, prune concepts that proved irrelevant.
Guiding Focus
Refinement is where ontologies become useful. The first pass is always rough — refinement makes it precise. Be willing to delete concepts that don't earn their place.
Available Tactics
- concept-decomposition — split over-broad concepts
- consistency-checking — verify refinements don't introduce conflicts
Budget Slice
| Metric | S | M | L |
|---|---|---|---|
| Merges performed | 2 | 5 | 12 |
| Gaps filled | 3 | 8 | 15 |
| Confidence updates | 5 | 15 | 30 |
State Ledger Template
| Metric | Target | Current | Status |
|---------------------|--------|---------|--------|
| Merges performed | X | 0 | ⬜ |
| Gaps filled | X | 0 | ⬜ |
| Confidence updates | X | 0 | ⬜ |
Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use |
|---|---|
| concept-decomposition | Tactic for breaking compound concepts into atomic parts — split over-broad concepts, identify sub-components, create child pages. |
| knowledge-structuring-consistency-checking | Tactic for verifying ontology consistency — detect contradictions, cycles, orphans, and type violations. |
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use |
|---|---|
| alias-resolution | SOP for detecting and resolving concept aliases — merge duplicate pages, redirect edges. |
| confidence-update | SOP for updating confidence scores on claims and evidence pages based on new information. |
| gap-detection | SOP for finding structural gaps in the ontology — missing concepts, thin branches, disconnected clusters. |
| merge-candidates | SOP for identifying near-duplicate concepts that should be merged. |
| ontology-export | SOP for exporting ontology summary — generate a readable overview of the current ontology state. |