Necklace of Hapiankhtifi
Description
Necklace, Hapiankhtifi. Middle Kingdom, Dynasty 12, ca. 1981–1802 B.C. Black obsidian ball beads; silver caps Silver. From: Tomb of Hapiankhtifi, Mummy, Meir, Middle Egypt, Egypt. Excavation: Khashaba excavations, 1910–12. Credit: Gift of J. Pierpont Morgan, 1912.
AI image analysis GPT-5.4-nano
Machine-generated from the object's image on Jul 2026. Not curatorial; treat deities, names, and signs below as the model's best reading, not authority.
Photograph of two Egyptian-style beaded necklaces made of dark spherical beads, with a central arrangement showing metal-capped ends and a small broken segment between beads.
The image shows two necklace strands laid on a light tan surface. Each strand consists of evenly sized dark, rounded (ball) beads connected with darker attachment elements, likely strung on a cord not clearly visible. At least one bead area includes metal caps; the most prominent caps/closures appear silvery-gray. One necklace includes a damaged or detached bead segment in the middle, revealing a rough, light-colored break surface and suggesting loss of some beads or cord tension. No hieroglyphic, Greek, Coptic, or Arabic inscriptions are visible anywhere on the beads or metal parts. No cartouches or royal names are visible. No deity iconography is present; only beadwork and metal fittings are apparent.
Connections
Cross-references (4)
- Wikidata-Q Q116281564 tier-1
- Collection-QID Q160236 tier-2 (wikidata-mediated)
- Inventory-Number 12.183.13a, b tier-2 (wikidata-mediated)
- MET-Object 546287 tier-2 (wikidata-mediated)
About this record's data
- From the source institution — accession, description, dimensions, and dating are as catalogued by Metropolitan Museum of Art — Egyptian Art (Open Access).
- AI-inferred — the image-analysis panel (deities, names, signs) is machine-generated and may be wrong.
- Approximate location — most map points are plotted at the site centroid, not the exact findspot.
- Inferred links — cross-references marked with a match method other than explicit-source-field were matched by us, not stated by the source.