METPO metals cohort: MetalElement + RareEarthElement + MetalRelevance#77
Merged
Conversation
New cohort under proposals/metpo_communitymech_metals_v1/ lifting three metal-related CommunityMech enums into METPO, following the metpo-proposal skill's new-cohort path. Independent of the v1 cohort (no shared rows), separate ID block (1008NNN / 2008NNN), separate subset tag (metpo_communitymech_metals_2026_05). Scoping choice: the per-element MetalElementEnum (17 values) and RareEarthElementEnum (16 values) values all carry meaning: CHEBI:xxxx annotations in the schema. Per the kg-microbe SKILL.md rule "use the existing IRI; record the alias upstream", this proposal does NOT mint per-element METPO classes. Only the grouping-parent classes are minted; the alias mapping flows into kg-microbe/mappings/metpo_existing_aliases.tsv when the cohort is copied upstream. Classes minted (8 rows): - METPO:1008000 community-relevant metal context (top-level domain class under METPO:1007100) - METPO:1008001 community-relevant metal element (enum-parent for MetalElementEnum, NO leaves - CHEBI IRIs serve as leaves) - METPO:1008002 community-relevant rare earth element (enum-parent for RareEarthElementEnum, NO leaves - CHEBI IRIs) - METPO:1008003 community metal relevance level (enum-parent for MetalRelevanceEnum) - METPO:1008010-1008013 the 4 MetalRelevance leaves (PRIMARY / SIGNIFICANT / INCIDENTAL / NOT_APPLICABLE) - these ARE minted because they have no CHEBI equivalent Predicates minted (3 rows): - METPO:2008000 has metal element present (community -> CHEBI:33521 metal cation) - range deliberately points at the CHEBI parent so per-element edges are CHEBI IRIs - METPO:2008001 has rare earth element present (community -> CHEBI:33530 rare earth atom group) - METPO:2008002 has metal relevance (community -> METPO:1008003 metal relevance level) Verification: 4/4 MetalRelevance leaves present, 0 per-element leaves leaked, 8/8 SC % parents resolve, both TSVs column-count clean. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds a new METPO “metals” cohort proposal under proposals/metpo_communitymech_metals_v1/, lifting CommunityMech’s metal/REE-related enums and slots into METPO ROBOT templates while reusing CHEBI IRIs for per-element values.
Changes:
- Introduces a narrative proposal describing scope, ID block, hierarchy decisions, and upstream workflow.
- Adds a ROBOT classes template minting 8 METPO classes (domain + enum parents + MetalRelevance leaves).
- Adds a ROBOT properties template minting 3 object properties linking
METPO:1007100(microbial community) to metal/REE presence and relevance.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| proposals/metpo_communitymech_metals_v1/proposal.md | Documents scoping choice (CHEBI reuse), hierarchy, and property/range rationale for the metals cohort. |
| proposals/metpo_communitymech_metals_v1/metpo_proposal_classes_robot.tsv | Defines the cohort’s new METPO classes (metal context + enum parents + relevance leaves). |
| proposals/metpo_communitymech_metals_v1/metpo_proposal_properties_robot.tsv | Defines object properties for metals/REE presence and metal relevance on microbial communities. |
Comments suppressed due to low confidence (1)
proposals/metpo_communitymech_metals_v1/metpo_proposal_properties_robot.tsv:4
- As with METPO:2008000, the
definitionincludes template-design rationale about why a particular CHEBI parent was chosen for the range. Since this field is emitted as the ontology definition (IAO:0000115), move the range-choice explanation toobservations/proposal.mdand keep the definition focused on the intended meaning of the relation.
METPO:2008001 has rare earth element present A relation between a microbial community and a CHEBI rare-earth-element atom or cation that is present in or processed by the community (lanthanides plus Y, Sc). Range points at the CHEBI rare-earth-atom parent so per-REE leaves remain CHEBI IRIs. CommunityMech:communitymech.yaml#MicrobialCommunity.rare_earth_elements_present owl:ObjectProperty METPO:1007100 CHEBI:33530 metpo_communitymech_metals_2026_05 HIGH rare-earth-element membership of community 0..* cardinality
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Five fixes for the five actionable Copilot comments:
- Properties TSV (METPO:2008000 has metal element present):
range CHEBI:33521 (metal cation) was too narrow because
MetalElementEnum mixes atom-form values (URANIUM/CHEBI:27214,
GOLD/CHEBI:29287, CHROMIUM/CHEBI:28073, TITANIUM/CHEBI:33341,
PALLADIUM/CHEBI:33373) with cation-form values. Broadened to
CHEBI:24431 (chemical entity) and rewrote the definition to
describe the relation semantics only ("a CHEBI chemical entity
that represents a metal element (atom or cation)..."). Moved
the heterogeneous-schema rationale to the observations column.
- Properties TSV (METPO:2008001 has rare earth element present):
same range fix (CHEBI:33530 -> CHEBI:24431) for consistency and
same definition-cleanup. RareEarthElementEnum values are all
cation-form, but using the same broad range keeps the two metal
predicates symmetric and forward-compatible if schema later adds
atom-form REE values.
- Classes TSV (METPO:1008001 community-relevant metal element):
cleaned the IAO:0000115 definition to describe the grouping
concept only ("a METPO grouping class for metal elements
relevant to microbial community function..."), removed the
"Per CommunityMech.schema... leaves SHOULD reuse CHEBI IRIs..."
policy text from the definition, moved it to the observations
column.
- Classes TSV (METPO:1008002 community-relevant rare earth element):
same definition cleanup as above.
- proposal.md: updated the predicate-proposals table and the
rationale paragraph to reflect the CHEBI:24431 range choice and
enumerate the specific atom-form values that motivated the
broadening. The "no METPO per-element leaves" intent is
preserved.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
New METPO cohort under `proposals/metpo_communitymech_metals_v1/` lifting three metal-related CommunityMech enums (`MetalElementEnum`, `RareEarthElementEnum`, `MetalRelevanceEnum`). Independent of the `metpo_communitymech_v1` cohort — separate ID block (`METPO:1008NNN` / `METPO:2008NNN`), separate subset tag (`metpo_communitymech_metals_2026_05`), separate proposal directory.
Scoping choice: CHEBI reuse for per-element values
The 17 `MetalElementEnum` and 16 `RareEarthElementEnum` permissible values all carry `meaning: CHEBI:xxxx` annotations in the schema. Per the upstream kg-microbe SKILL.md rule "if the lifted concept already exists in METPO under a different label, use the existing IRI; record the alias upstream", this proposal does not mint per-element METPO classes. Only the grouping-parent classes are minted; per-element CHEBI IRIs flow into `kg-microbe/mappings/metpo_existing_aliases.tsv` when the cohort is copied upstream.
Classes minted (8 rows)
The 4 MetalRelevance leaves are minted as fresh METPO classes — they're qualitative severity categories with no CHEBI equivalent.
Predicates minted (3 rows)
The first two predicates deliberately point `RANGE` at a CHEBI parent so per-element edges (e.g., `community has metal element present CHEBI:29033`) validate via CHEBI's existing `CHEBI:29033 ⊑ CHEBI:33521` axiom — no METPO per-element leaf needed.
Verification
Test plan
🤖 Generated with Claude Code