OpenAI Education US

Zelma

Enterprise Knowledge Search · Real-time Analytics

Zelma needed to make fragmented K-12 assessment data usable for parents, educators, and policymakers because the information was scattered across portals and formats and was too hard for most people to query or visualize.

around a 77 percent proficiency rate
top 5 highest performing non-charter school districts in math in Minnesota
views that have historically taken district leadership teams hours or even days to generate

Reported impact

Business outcome

Zelma made school-performance data far easier to query, visualize, and discuss, giving leaders and families faster access to insights that previously took hours or days to assemble.

  • Customer Experience
  • Productivity Improvement

Solution

Zelma turns public education data into a conversational analytics experience by combining a cleaned national dataset with GPT-4 and the OpenAI API. Brown University researchers first gathered and normalized standardized-test data into one format, then Novy used function calling to tell GPT-4 which charts, fields, and views to use when answering user questions. For the Ask a Question interface, Zelma fine-tuned a model to provide data-aware typeahead suggestions and embedded known-good example graphs in a vector database to improve accuracy on edge cases. Questions in plain language enter the interface, the OpenAI-backed orchestration layer maps them to relevant datasets and visuals, and Zelma returns charts, SQL logic, and plain-language context about caveats such as assessment changes. That design makes school-performance analysis faster, more transparent, and more accessible to nontechnical audiences.

Data flow

Standardized-test data is cleaned into a uniform dataset, user questions are sent through the OpenAI API to GPT-4 with function-calling guidance, and the resulting answers return charts, supporting logic, and contextual explanations grounded in Zelma's education data.

Solution architecture

3 components · 3 layers
  1. Compute
    • GPT-4 Interprets natural-language education questions and selects the right visuals and fields for answers.
  2. Storage
    • vector database Stores known-good example graphs that improve accuracy on difficult edge cases.
  3. Orchestration
    • OpenAI API Connects Zelma's application logic to GPT-backed question answering and chart selection workflows.

Architecture clues

  • Function calling is used to decide which visuals and fields to display
  • Known-good graphs are embedded in a vector database to improve accuracy
  • The Ask a Question view uses a fine-tuned model for data-aware typeahead
  • Zelma shows the SQL code behind answers for transparency

Evidence from the source

Novy leveraged function calling to tell GPT-4 which visuals and fields to choose from in displaying the data
They embedded and stored known-good example graphs in a vector database to improve accuracy on difficult edge cases
They fine-tuned a model to create a data-aware type-ahead
Zelma offers K-12 superintendents an intuitive, conversational platform to instantly visualize student learning data
Transparency Evidence & methodology 70/100 reference value · 87% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value70/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. OpenAI

    Zelma customer story

    First-party
    https://openai.com/index/zelma/
    Source type
    Vendor-published customer story
    Published
    Apr 1, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Apr 1, 2024 · OpenAI · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.