
RelBench
7 posts

RelBench
@RelBench
RelBench: Relational Deep Learning Benchmark



Relational Foundation Models face a scaling problem: diverse training datasets are rarely public due to privacy constraints 🔒. 🚀 We are excited to introduce "PluRel": a framework that synthesizes diverse multi-table relational databases from scratch, unlocking scaling laws for RFMs. 🧵 Kudos to the amazing collaborators at @StanfordAILab @Kumo_ai_team , and @SAP : @_rishabhranjan_ @VHudovernik @vijaypradwi @johanneshoffart @guestrin @jure

Relational Foundation Models face a scaling problem: diverse training datasets are rarely public due to privacy constraints 🔒. 🚀 We are excited to introduce "PluRel": a framework that synthesizes diverse multi-table relational databases from scratch, unlocking scaling laws for RFMs. 🧵 Kudos to the amazing collaborators at @StanfordAILab @Kumo_ai_team , and @SAP : @_rishabhranjan_ @VHudovernik @vijaypradwi @johanneshoffart @guestrin @jure

🚀 Announcing RelBench V2, a major update to our benchmark for foundation models on relational data! With V2, we are significantly expanding the benchmark’s scope to catalyze further research in Relational Deep Learning (RDL) and Relational Foundation Models (RFMs). Key features: 🍺 4 new databases, spanning domains like e-commerce and beer reviews to scientific research and clinical healthcare. 🧩 40 new predictive tasks, including 28 autocomplete tasks, across new and existing databases. 🔌 External data integrations: 70+ datasets from CTU, 7 datasets from 4DBInfer, and your own data via SQL connector, all in RelBench format. 🛠️ Bug fixes and performance improvements. 🔥 Introducing autocomplete tasks: As opposed to forecasting tasks, autocomplete tasks predict existing columns in the database. We found that models need to deeply understand the relational context to autocomplete database fields, a critical capability that expands the scope of real-world RDL applications. Learn more: 🌐 Website: relbench.stanford.edu 💻 GitHub: github.com/snap-stanford/… Huge thanks to @justingu32 @_rishabhranjan_ @jakub_peleska @VHudovernik @CKanatsoulis @fengyuli607, Tang Haiming, Alistiq and everyone else who contributed to our GitHub for making this possible!





