Looking for usage documentation? Check out Relational predictions.
DatabaseSpec
View source build_dataset / UserDataset (mirroring
RelBench’s Database vs Dataset split).
DatabaseSpec.from_yaml
View source path if given; relative paths and the
default <name>.parquet resolve against data_dir, or the YAML’s own
directory if data_dir is omitted - so the schema stays portable and
materialize_relbench can supply the files.
PredictiveTaskSpec
View source query is a DuckDB statement that joins timestamp_df (a single column
timestamp holding the anchor times) against the database tables - referenced by
their names - and returns exactly time_col, entity_col and target_col,
computing the label over the forward window (t, t + timedelta]. The literal
{timedelta} in the query is replaced with the string form of timedelta, e.g.
INTERVAL "{timedelta}".
val_timestamp / test_timestamp are the tuning and final split cutoffs.
The database schema lives separately in a DatabaseSpec.
task_type accepts the RelBench enum or the strings "binary_classification" /
"regression"; timedelta accepts a pandas.Timedelta or anything it can parse.