Is the Oxford Academic ontology-evolution paper (doi:10.1093/database/baae133) peer-reviewed, and do its change-type categories map onto the four SEEK mechanisms?

The paper in question is "A change language for ontologies and knowledge graphs" (Hegde, Vendetti, Goutte-Gattat, Caufield, Graybeal, Harris, Karam, Kindermann, Matentzoglu, Overton, Musen & Mungall), published in Database, Volume 2025, article baae133, DOI 10.1093/database/baae133. It introduces KGCL (Knowledge Graph Change Language), a data model and controlled natural language for describing changes to ontologies and knowledge graphs.

Claim 1 — The paper is peer-reviewed

Claim type: historical/definitional (publication status) Source tier required: Tier 3–4 acceptable; source obtained is Tier 1

The article carries a full journal editorial workflow, displayed on both the publisher's article page and the PubMed Central mirror: "Received 2024 Sep 20; Revised 2024 Nov 21; Accepted 2024 Dec 30; Published 2025 Jan 22." This received/revised/accepted/published sequence is standard evidence of a peer-review editorial process, and the article is indexed in PubMed/MEDLINE (PMID 39841813) and mirrored in PubMed Central (PMC11753292), both of which apply their own inclusion vetting on top of the journal's own process. Database is an established Oxford University Press journal in the biocuration space.

Exact quoted phrase (from the article-of-record page and its PMC mirror, cross-checked):

• "Received 2024 Sep 20; Revised 2024 Nov 21; Accepted 2024 Dec 30; Published 2025 Jan 22"

provenance: Hegde, H. et al. (2025). "A change language for ontologies and knowledge graphs." Database, 2025, baae133. https://academic.oup.com/database/article/doi/10.1093/database/baae133/7972659 ; cross-checked at https://pmc.ncbi.nlm.nih.gov/articles/PMC11753292/

Verdict on this half of the question: yes, peer-reviewed — confirmed, not unverified.

Claim 2 — The paper's actual implemented change-type taxonomy is NodeChange/EdgeChange, not a flat add/modify/merge/split scheme

Claim type: technical mechanism Source tier required: Tier 1–2 ✓ (Tier 1 obtained)

Table 1 of the paper defines two top-level change categories, each with named subtypes. NodeChange subtypes: NodeRename, NodeObsoletion, NodeDeletion, ClassCreation, SynonymReplacement, NewTextDefinition, RemoveTextDefinition, NodeTextDefinitionChange, NewSynonym, RemoveSynonym. EdgeChange subtypes: EdgeCreation, EdgeDeletion, NodeMove, PredicateChange. This list was extracted from the PMC full-text mirror and cross-checked against the publisher's article page; both fetches returned the same subtype names.

provenance: same article, Table 1. https://pmc.ncbi.nlm.nih.gov/articles/PMC11753292/ ; cross-checked at https://academic.oup.com/database/article/doi/10.1093/database/baae133/7972659

Claim 3 — The paper's introduction frames ontology changes in general terms that include "merging," but its formal taxonomy does not implement merge as a first-class operation, and does not implement split at all

Claim type: technical mechanism Source tier required: Tier 1–2 ✓ (Tier 1 obtained)

The introduction states, as informal framing (not as the paper's own implemented taxonomy): "Changes to ontologies generally fall into several categories: adding a new element, obsoleting an existing element, merging two elements, and adding/deleting/modifying information associated with an element." Note this sentence names add, obsolete, merge, and modify — it does not mention split at all, even informally.

Separately, in discussing scope and future work, the paper explicitly places both merge and split outside the current implementation: "Instance-level (ABox) changes, like instance addition or deletion, and heuristic changes, such as concept merge and split, are yet to be considered." This sentence was independently retrieved from both the OUP article page and the PMC full-text mirror with matching wording.

Exact quoted phrases (Tier 1):

• "Changes to ontologies generally fall into several categories: adding a new element, obsoleting an existing element, merging two elements, and adding/deleting/modifying information associated with an element"
• "Instance-level (ABox) changes, like instance addition or deletion, and heuristic changes, such as concept merge and split, are yet to be considered"

provenance: same article, Introduction and Discussion/Future Work sections. https://academic.oup.com/database/article/doi/10.1093/database/baae133/7972659 ; cross-checked at https://pmc.ncbi.nlm.nih.gov/articles/PMC11753292/

Answer to the core question

The paper is peer-reviewed (Claim 1). But the premise embedded in the harvested lead — that the paper's change-type categories are cleanly "add/modify/merge/split" — is only partially accurate. The paper's actually-implemented taxonomy (KGCL Table 1, Claim 2) is built from NodeChange and EdgeChange subtypes: creation (add), rename/definition/synonym edits and PredicateChange (modify), and NodeMove (a topology-changing edge operation). "Merge" appears only in the paper's informal introductory framing of the general problem space, not as a named, implemented KGCL change type. "Split" is not part of the general framing sentence at all, and both merge and split are explicitly flagged by the authors as unimplemented "heuristic changes... yet to be considered" for future work (Claim 3).

So: add and modify map cleanly onto the paper's real taxonomy; merge is acknowledged conceptually but not implemented; split is not implemented and barely mentioned. The four-term "add/modify/merge/split" framing from the harvested lead over-states how symmetrical the paper's actual coverage is.