Baseball / structured data
Groundball
A baseball question-answering app. Ask it something like "Who had the most RBIs in 1962?" and it answers with real numbers and links showing where each answer came from. AI can figure out what to look up, but it doesn't write the factual answer. The app builds that from checked data. Its local statistics engine also runs fully offline, with no AI.
From question to evidence
- Ask a supported question. The app can handle familiar statistics questions without AI. When AI is available, it can figure out which data or sources to look up.
- Check the request. The app checks that the lookup is one it supports. It rejects custom database commands and formulas.
- Look up the facts. Historical numbers come from the local database. Current information comes from sources the app checks before using.
- See where the answer came from. Each claim shows its source. For statistics, you can also inspect the database query and the data behind the result.
AI can help work out what to look up. It does not write the factual answer. The app builds that answer from real statistics and checked source records, with a source for every claim. Once its data is installed, the local statistics engine runs with no AI and no internet connection.
A question to try
Who had the most RBIs in 1962?
Try it in the public app, then look at the numbers and the source evidence behind the result. The repository explains how to run it locally in a browser or from the command line.
Project scope
I built this as a personal project with AI-assisted development. It does not answer every baseball question. It supports historical statistics, reviewed explanations of stats, and limited current information such as batting leaders and tentative probable pitchers. It reports missing evidence and declines unsupported requests.
The public app uses AI when available to understand questions, but the local statistics engine does not need it. It needs no account or connection to my Mac. The older private blog demo is a separate entry point. The app does not generate player biographies or open-ended stories.
Supported requests can combine a few operations and use follow-up context. This is a bounded assistant, not an autonomous research agent or a promise to answer every baseball question.