DUFMech

All families / PF09931

PF09931: Phage_phiJL001_Gp84_N

Baseplate hub protein, N-terminal attachment domain

Curation status
SEEDED
Seed status
EX DUF
Characterization
UNSCORED

Grounding

PF09931: Baseplate hub protein, N-terminal attachment domain
No integrated InterPro identifier in the snapshot.

Source description

This entry represents the N-terminal attachment domain (residues 1-142) of the baseplate hub protein found in phages and gene transfer agents [InterPro reference PUB00153971]. This domain is part of a multi-domain protein that also contains an ion-binding domain (143-167, 250-263), an oligosaccharide-binding domain (168-249), and a C-terminal clip domain (264-296). The attachment domain enables binding to the distal tail proteins and helps anchor the hub protein within the baseplate structure. This family is found almost exclusively in phages and prophage regions of bacterial genomes, including the Rhodobacter capsulatus gene transfer agent.

Evidence and references

Source descriptions and links are provenance, not independent functional validation.

Evidence counts: not scored.

Curated functional assertions

No curated functional assertions supplied.

Protein sequence examples

No sibling protein candidate in the scanned commits.

Pfam membership is not functional evidence. Whole-protein sequences do not establish domain boundaries. A coverage gap here is not absence from UniProt.

Sequences and metadata: UniProt Consortium, CC BY 4.0.

Domain matches

No residue-level domain match evidence is available in this build. Structure and AlphaFold counters do not supply coordinates or establish function.

Snapshot counters

proteins
2,302
matches
2,303
proteomes
1,940
taxa
3,191
structures
6
alphafold models
1,505
domain architectures
12

Classification basis

pfam previous unknown name

No scoring reasons supplied.

Related Mech records

This family joined the worklist after the frozen cross-Mech scan, so other Mechs were not searched for it. Missing links here are not evidence that other Mechs lack it; rows shown come from mentions of a former DUF/UPF name.

No cross-Mech examples are present in the supplied snapshot.

Curation history and reviews

No retained curation events supplied.

No retained review supplied.

Record source

data/families/PF09931.yaml
Family YAML in this build

Download this family (JSON)

Status and evidence

Seed status
A name-based classification of frozen InterPro/Pfam metadata. UNKNOWN CANDIDATE means the metadata explicitly says the function is unknown. KNOWN HISTORICAL DUF means a DUF name matched without that wording; this heuristic is not proof of a known function and does not establish experimental characterization. EX DUF means Pfam renamed the family away from a DUF/UPF name, as recorded in Pfam's previous identifiers; a rename usually follows published work on some members but is naming history, not proof of function for every member. Some EX DUF families' current names or descriptions still say the function is unknown; their classification basis lists this, and scoring does not treat them as characterized. FALSE POSITIVE TEXT HIT means the naming rules did not match.
Characterization
A separate evidence-scoring result. UNSCORED means no score has been calculated; it is not evidence that the family lacks a known function. Missing scores are not negative evidence. PARTIALLY CHARACTERIZED has partial support; KNOWN HISTORICAL DUF can inherit the seed label or reflect a known-function signal. Neither label implies experimental validation.
Evidence counts
Source-specific signals, not unique proteins, publications, or confidence scores. Known counts Rhea reactions and experimentally supported GO molecular-function annotations. Partial counts functional/domain assignments. Context counts structural, environmental, orthology, interaction and neighborhood signals; context alone does not assign function. Repeated annotations may not be independent.
Curation status
Reported separately from seed classification and characterization. SNAPSHOT ONLY means no curated metadata was supplied for this build. SEEDED denotes a source-derived record, not an expert-reviewed functional claim.
Missing counts
Not available means the source did not supply that counter. A zero is a reported count. Not scored means evidence counts are unavailable.