Challenge

Trace the Ace

Predict the learning gains from a tutoring session measured by quiz performance in this tutoring outcomes prediction challenge

Tasks
Tutoring
Data types
Human transcript
Tabular
$50,000 in prizes
4 weeks left model submissions
7 weeks left solution write-up
639 joined
Image generated using Gemini

Problem description

In this competition, your task is to predict student quiz performance based on transcripts of tutoring lessons. Given a student-tutor transcript, your goal is to predict whether the student answered the next question on the same topic correctly. By participating, you can help advance our understanding of:

  • Which tutoring strategies are most effective in supporting student learning.
  • How to perform student knowledge tracing based on dialogue alone. Effectively monitoring student understanding without needing to take time for costly testing enables teachers to better respond to student needs.

Insights from this work could ultimately contribute to better tutoring systems, improved instructional support, and more equitable access to high-quality educational experiences at scale.

Not sure where to start? Read over the basic steps in the "How to compete" section of the Home page.

Modeling goals

A key goal of this challenge is to discover generalizable insights based on exploration of modeling approaches. The top 15 teams on the final leaderboard will be invited to submit a solution write-up describing their key insights, methodology, and results. All prizes will be based on a combination of leaderboard performance and write-up quality.

During model development, focus on uncovering useful insights related to tutoring effectiveness and student knowledge tracing, rather than solely maximizing model performance. For example:

  • What can you learn from trying different approaches to feature engineering? In this high-dimensional data, how can you extract generalizable features?
  • Can you identify different types of tutoring moves? What tutoring moves are most effective?
  • Many tutoring transcripts are very long. Can you identify "key moments" that provide insight into student understanding?

Approaches that focus on uncovering insights relevant to educational research will make for the strongest write-up submissions.


Dataset

The data for this competition are real student-tutor conversations paired with measures of student learning outcomes, collected in partnership with Third Space Learning (TSL) and Eedi. See the About page for details.

Each sample is a different student response. Each represents a unique combination of tutoring session and learning objective. A single tutoring session may therefore correspond to multiple samples if multiple learning objectives were completed.

Features

The primary feature provided in this competition is the conversation between the student and tutor, along with a short description of the learning objective being tested. Strong submissions will focus on identifying signals in the session transcripts, rather than from the learning objective description alone.

Training features are provided in two components:

.
├── train_features.csv
└── train_transcripts
    ├── abc.csv
    ├── ...
    └── xyz.csv

The train_features.csv file contains response-level metadata:

  • response_id (str): unique identifier for the sample
  • session_id (str): session identifier linking to a transcript file
  • learning_objective (str): short description of the learning objective associated with the assessment question.

The train_transcripts/ directory contains one CSV file per tutoring session. The file name corresponds to session_id. For example, a session with id abc is saved at train_transcripts/abc.csv. Each transcript file contains the following columns:

  • session_id (str): unique session identifier
  • utterance_id (str): unique utterance identifier within the session
  • role (str): speaker role, either tutor or student
  • content (str): transcript text for the utterance
  • timestamp (datetime): time the utterance was sent

Each row is a different utterance.

Labels

Training labels indicate whether a student answered the next assessment question correctly following the tutoring interaction.

Labels are provided in CSV format with the following columns:

  • response_id (str): unique sample identifier
  • correct (float): target label (0.0 = incorrect, 1.0 = correct)

Example:

response_id,correct
abc,0.0
def,0.0
xyz,1.0

External data and models

Participants may use external datasets and pretrained models provided they are publicly available and openly licensed. See the external data section in the challenge rules for further details.


Performance metric

Submissions will be evaluated using log loss. Log loss penalizes confident but incorrect predictions. It rewards confidence scores that are well-calibrated probabilities, meaning that they accurately reflect the long-run probability of being correct. This is an error metric, so a lower value is better. Log loss for a single observation is calculated as:

$$LogLoss = -(y \log (p) + (1 - y) \log (1 - p))$$

|$y$| is a binary variable indicating whether the student actually answered the question correctly. |$p$| is the user-predicted probability that the student was correct. The loss for the entire dataset is the average loss across all observations.

Log loss can often be improved with calibration. A well-calibrated model outputs predictions that are directly interpretable as probabilities.

ROC AUC will be displayed on the leaderboard for reference, but does not impact position on the leaderboard.

Submission format

This is a code execution challenge! Rather than submitting your predicted labels, you will package your trained model and the prediction code and submit that for containerized execution. Inference-time internet access will not be available, and all models and dependencies must be packaged with the submission.

Participants must submit predictions as probabilities between 0 and 1 representing the likelihood that the student answered the next question correctly. Submissions should be CSV files with the following columns:

  • response_id (str): unique sample identifier
  • probability (float): predicted probability of correctness

For example, the first few rows of your test predictions might be:

response_id,probability
aaafrcy,0.5
aabbmio,0.1
aabpxat,0.9

Solution write-up

The solution write-up is an opportunity to describe the ideas, methods, and insights behind your competition solution beyond its leaderboard performance. 1st-3rd place prizes will be awarded based on a combination of leaderboard ranking and write-up quality. Only the top 15 teams on the final leaderboard will be eligible to submit write-ups and win overall prizes. Write-ups will be accepted after the leaderboard has closed.

The top submissions will be invited to develop their write-up into a full academic paper for publication. Write-ups should provide a summary of key findings that are useful to the field of education research, as well as key ideas that would be discussed in a full paper. Solutions should focus on generating insights from the tutoring session transcript, rather than from the learning objective description alone.

Format requirements:

  • PDF submission
  • Maximum of 4 pages, including figures and tables but not references
  • Page Size: 8.5x11" with 1" margins
  • Font: Minimum 11pt for main text, 10pt font for figures and tables
  • Minimum single-line spacing

Write-up evaluation criteria

Relevance (35%)

  • Does the report surface meaningful and actionable insights that are relevant to the core tasks of (1) understanding what makes tutoring effective and (2) student knowledge tracing?
  • Does the report provide actionable guidance for other researchers based on those findings?

Generalizability (35%)

  • Would the approach and conclusions generalize to other chat-based tutoring setups? How well does the report demonstrate generalizability?

Communication (15%)

  • Is the report well written and easy to understand? Is it accessible to an audience of education researchers who may not be experts in machine learning?

Rigor (15%)

  • Is this submission based on appropriate and correctly implemented methodology?

Write-up template

Strong reports will include the following sections:

  1. Key findings. Summarize the most important takeaways from your work, with an emphasis on insights that would be most useful for education researchers, practitioners, or future developers of tutoring systems. This section should connect your modeling results back to what they suggest about tutoring sessions, student learning, and knowledge tracing. Possible topics include:

    • Important tutoring or interaction patterns associated with learning gains
    • Especially informative modeling features
    • Which modeling and data processing strategies are effective and why
    • Implications for teaching and educational research
    • An example of a takeaway that would not be of interest: how to predict probability of correctness based on inferred difficulty of the learning objective description, without reference to the session transcript
  2. Methodology. Describe your overall approach. Visualizations, tables, and figures are encouraged where they improve clarity or interpretability. Focus on the aspects of your approach that would be discussed in a full paper. You are encouraged to explain the reasoning behind methodological choices. Possible topics include:

    • Any especially important or novel aspects of your solution.
    • Preprocessing and feature engineering
    • Modeling approaches and evaluation methods
    • Explainability or interpretability techniques
    • Validation strategies
  3. Extensions & generalizability. Discuss how your approach and findings could be extended beyond the competition. This section should help reviewers understand both the broader applicability of your work and what additional analyses would strengthen it as a research contribution. Possible questions to consider:

    • How well would your approach and your key findings generalize to other tutoring environments?
    • What are the main risks, limitations, or open questions? Under what circumstances should users trust or be cautious about the model outputs?
    • How could the methods or findings be extended in future work?

Good luck!


Good luck and enjoy this problem! If you have any questions you can always visit the user forum!