Glyph GPT |

𓉡𓀬𓉢

Historic epochs iterating...

/ / / / 𓎛 𓃀 𓇑 𓇑 𓏏 𓎺 𓏤 𓏤 𓐍 𓈖 𓆑 𓅱 𓎺 𓏤 𓏤 𓇋 𓈙 𓂧 𓈓 𓎺 𓏤 𓏤 𓋴 𓄡 𓏏 𓈓 𓎺 𓌉 𓏏 𓎺 𓏤 𓏤 𓋴 𓄡 𓏏 𓇅 𓎺 𓏤 𓏤 𓊃 𓏏 𓇠 𓂝 𓎼 𓏏 𓎺 𓏤 𓏤 𓇠 𓂝 𓎼 𓏏 𓎺 𓏤 𓏤 𓃀 𓅡 𓏏 𓇠 𓎺 𓏤 𓏤 𓈖 𓃀 𓋴 𓎺 𓏤 𓏤 𓏏 𓈖 𓃀 𓋴 𓈓 𓎺 𓏤 𓏤 𓎛 𓅱 𓂝 𓇹 𓈓 𓎺 𓏤 𓏤 𓐍 𓏏 𓎟 𓃀 𓇜 𓏏 𓆶 𓎟 𓏏 𓎛 𓈖 𓎡 𓂠 𓎟 𓏤 𓐜 𓋴 𓅱 𓊰 𓄂 𓎛 𓅱 𓂧 𓏐 𓏊 𓏖 𓏤 𓏤 𓏤 𓊪 𓊃 𓈖 𓏖 𓏤 𓏤 𓏤 𓏤 𓈙 𓈖 𓋴 𓏐 𓏤 𓏤 𓏤 𓏤 𓊪 𓊃 𓈖 𓏖 𓏤 𓏤 𓏤 𓏤 𓏏 𓏶 𓇿 𓏤 𓏤 𓏤 𓏤 𓐍 𓈖 𓆑 𓅱 𓎺 𓏤 𓏤 𓏤 𓏤 𓏤 𓎛 𓃀 𓇑 𓇑 𓏏 𓈓 𓎺 𓏤 𓏤 𓏤 𓏤 𓈎 𓎛 𓌚 𓏑 𓏤 𓏤 𓏤 𓏤 𓏤 𓇋 𓂧 𓄿 𓏏 𓏖 𓇉 𓎡 𓏤 𓏤 𓏤 𓏤 𓏏 𓏐 𓄿 𓈙 𓂋 / 𓏤 𓏤 𓏤 𓏤 𓌉
2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 por 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 portions, 2 por 2 portions, 4 portions, 4 portions, 4 portions, 4 portions, 4 portions, 4 portions, 4 portions, 4 portions, 4 portions, 4 portions, 4 portions, 4 portions, 4 portions, 4 portions, 4 por There is no translation
Text copied

Gardiner codes: / / / / V28 D58 M22 M22 X1 W10 Z1 Z1 Aa1 N35 I9 G43 W10 Z1 Z1 M17 N37 D46 N33A W10 Z1 Z1 S29 F32 X1 N33A W10 T3 X1 W10 Z1 Z1 S29 F32 X1 M13 W10 Z1 Z1 O34 X1 M33 D36 W11 X1 W10 Z1 Z1 M33 D36 W11 X1 W10 Z1 Z1 D58 G29 X1 M33 W10 Z1 Z1 N35 D58 S29 W10 Z1 Z1 X1 N35 D58 S29 N33A W10 Z1 Z1 V28 G43 D36 N11 N33A W10 Z1 Z1 Aa1 X1 V30 D58 M30 X1 M7 V30 X1 V28 N35 V31 D39 V30 Z1 Aa14 S29 G43 R2 F4 V28 G43 D46 X2 W22 X6 Z1 Z1 Z1 Q3 O34 N35 X6 Z1 Z1 Z1 Z1 N37 N35 S29 X2 Z1 Z1 Z1 Z1 Q3 O34 N35 X6 Z1 Z1 Z1 Z1 X

How does it work?

GlyphGPT begins with nanoGPT, Andrej Karpathy's GPT architecture implementation, trained from scratch exclusively on hieroglyphic texts painstakingly prepared by Mattia De Cao. Optimized with Claude Code autoresearch. This generates streams of hieroglyphic sequences, which we then translate into English using Mattia's hiero-transformer - which iteself is based on Facebook's M2M-100 translation model, fine-tuned on the same hieroglyphics dataset. Essentially a mini AI learns to babble Middle and Old Egyptian, and big AI does its best to translate that into English. Both models have some room for improvement, but what could go wrong? Actually one thing for sure going wrong, Gardner notation has a larger vocabulary than unicode; so [Z3A] indicates the A variant of [Z3] but it is displayed as [𓏪A].

Contact

EgyptGPT GitHub

Thanks to Andrej Karpathy's for NanoGPT, and Mattia De Cao for releasing the translation model and dataset.