F1 Temporal Knowledge Benchmark
A benchmark for measuring how well language models track fast-changing, verifiable facts — using Formula 1 standings, results, and records as ground truth. F1 facts change every ~2 weeks during the season, making this domain a natural, continuously-refreshed test of temporal knowledge and hallucination in LLMs.
Why F1?
Most knowledge benchmarks go stale the moment a model is trained. F1 gives us a domain where "true as of last week" and "true as of last year" are meaningfully different — a clean way to measure whether a model knows what it knows, or confidently guesses.
Install
pip install f1-temporal-bench
Setup
Evaluating models requires a Hugging Face access token with Inference Providers permission enabled.
- Create a token at huggingface.co/settings/tokens (the default "Read" preset includes this)
- Export it in your shell:
export HF_TOKEN=hf_your_token_here
- Make sure at least one Inference Provider is enabled on your account at huggingface.co/settings/inference-providers. This project currently queries models through Featherless AI, which hosts the broadest range of open instruct models — enable it there.
Usage
# Check the dataset is well-formed
f1-temporal-bench validate
# Evaluate a model via the HF Inference API
f1-temporal-bench run --model Qwen/Qwen2.5-7B-Instruct --output results.json
# Evaluate a model locally instead (requires the 'local-models' extra)
pip install "f1-temporal-bench[local-models]"
f1-temporal-bench run --model Qwen/Qwen2.5-7B-Instruct --local
Picking a model
Not every model on the Hub is served by an Inference Provider. Before running an eval, you can check what's live for a given model:
curl -s "https://huggingface.co/api/models/MODEL_ID?expand[]=inferenceProviderMapping" | python3 -m json.tool
Look for an entry with "status": "live" — that's the provider that will
serve the request.
Metrics
- Accuracy — exact/alias match against ground truth
- Confidently wrong rate — model gives a specific, wrong answer instead of hedging
- Refusal rate — model declines to answer / says it doesn't know
Contributing questions
Add new rows to data/questions.jsonl after each race weekend. Each row
follows this schema:
{"id": "unique-id", "date": "YYYY-MM-DD", "question": "...", "answer": "...", "aliases": ["..."], "category": "...", "season": 2026, "round": 1}
Run f1-temporal-bench validate before committing.
Development
git clone https://github.com/spragada4/f1-temporal-bench.git
cd f1-temporal-bench
python3 -m venv .venv
source .venv/bin/activate
pip install --upgrade pip
pip install -e ".[dev]"
pytest
Releases
Tagged pushes (vX.Y.Z) trigger an automated build, PyPI publish, and
GitHub Release via GitHub Actions. See .github/workflows/release.yml.
Roadmap
- Automated dataset updates via GitHub Actions after each race
- Multi-model leaderboard published to GitHub Pages
- Dataset published on the Hugging Face Hub with versioned season snapshots
License
MIT
Release files for f1-temporal-bench 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| f1_temporal_bench-0.1.2.tar.gz | 6.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| f1_temporal_bench-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.7 kB
Release files / f1_temporal_bench-0.1.2.tar.gz
| Download URL | f1_temporal_bench-0.1.2.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00425ab6e66c75b5750521b9db98960bff44ef86530c9049982bd5a78c7a699d
|
|
BLAKE2b-256 checksum How to use checksums |
c962a95a349a7d1f8f3e43309264efc12296367a96eb695c20d8814923b13be7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.
Transparency logRelease files / f1_temporal_bench-0.1.2-py3-none-any.whl
| Download URL | f1_temporal_bench-0.1.2-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f2d076f1273f8f95f74c3689c389132340d2879c2f8357a4c4336524c160fb0d
|
|
BLAKE2b-256 checksum How to use checksums |
3f798535658ccf6af655d23a0b35512c3083b706ffb0353118e2ebf54fe34e78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.
Transparency log