Problem Corpus Extraction
Illustration: Keep the question source and the status of its solution visible.A useful practice collection needs more than a list of questions: it needs to say where each question came from and what kind of answer accompanies it. Problem Corpus Extraction gathers exercises from course materials and preserves that distinction. A student’s handwritten attempt stays labelled as an attempt.
That choice came from inspecting the available materials. Some exercises had no answer; others had the student’s working beside them, with no basis for calling it an answer key. The stored records therefore mark accompanying text as a student attempt or leave the solution absent. The extractor does not turn an unverified derivation into a verified one.
A clearly illustrative card, rather than an excerpt from private coursework:
Question: Show that the sum of two even integers is even.
Source: Example worksheet, Question 2.
Accompanying work: Student attempt, not checked.
The tool first detects numbered question boundaries, then asks a model to separate each statement from any accompanying solution and assign a short topic label. It stores the results by course and skips unchanged files on later runs. A failed extraction can be recorded without discarding other successful questions.
A September 2026 math-camp run produced 196 records from eight problem-set files, with no reported extraction failures. Four slide files had no recognized numbered-question boundaries and were skipped. That is evidence of the run’s output, not an accuracy audit of all 196 statements or solutions.
The current tool stops at creating the stored collection. Connecting it to Problem Generation remains separate work; that generator currently retrieves its own examples. The README explains the output and provenance rules.
