Structured Data· 3 min read

How We Test: The Methodology Behind Every Number We Publish

Every number we publish comes from somewhere. This article is the map: five tools we built ourselves, what each one actually measures, and where you can check our work yourself.

Measured from research-data (DOI v0.1.0)

Runs per figure
5
Internal tools

Two different questions

When people ask "how good is AI at Indonesian", there are actually two different questions hiding inside that, and we measure them in two ways that cannot substitute for each other.

Test Data (Benchmark)

Closed questions with one documented correct answer, such as applying standard PUEBI spelling rules. Models are scored right or wrong against that answer key.

AI Battle (Arena)

Open-ended answers to the same question, judged directly by readers through a blind vote. Suited to registers where correctness is decided by speaker acceptance rather than a rulebook, such as slang or regional languages.

A model can be strong at one and ordinary at the other, and that is exactly what we want to show, not hide behind a single blended score.

The tools behind it

The numbers we publish do not come from one tool. They come from several that lean on each other.

Corpus

Before anything can be tested, there has to be material to test with. We collect real Indonesian and regional-language usage, not invented examples, as raw material for both the dictionary and the test data.

Dictionary and corrector

Our internal correction tool checks Indonesian spelling and grammar. It is judged not by how often it is right on examples we picked ourselves, but by how often it is wrong on real text it has never seen, because a correction tool tested only on easy examples will always look flawless.

One component uses a quantised (ONNX) IndoBERT model to rerank spelling suggestions. We measured this path as more accurate but also considerably slower, so it currently sits disabled in production until that balance makes more sense.

Test data (Benchmark)

This is what tests third-party AI models on closed questions, spanning standard spelling, normalising informal register, and regional speech levels. We write the questions ourselves from our verified corpus, and a portion is deliberately never published.

Data layer audit

Separate from the three above, there is a check on our own dictionary: whether entries, meanings, examples, and the relationships between words actually hold together, checked directly against what is running in production. This looks inward, not at an outside AI model.

AI Battle (Arena)

This is where readers do the judging. Two models answer the same question with no names shown, and you pick the better answer. The results build a model ranking for Indonesian, and going forward we plan for the arena's results to also feed research articles, not stand alone as just a leaderboard.

Rules we hold ourselves to

  • Test data is written from our own verified corpus, not lifted from benchmarks already circulating online. A model cannot have memorised a question that did not exist before we wrote it.
  • A portion of items is deliberately never published, so it stays usable for checking whether a model has seen the material before.
  • Model names are hidden in AI Battle until you vote, and which side an answer appears on is randomised by the server, so what gets judged is the writing, not the brand.
  • Every published figure links to its data file in a public repository, pinned to the version it was cited at.
The figures we publish come from three repeated runs, not one. The same model can score differently on identical questions, and we report that gap as variance instead of hiding it.

Want to check the data file yourself, or cite the exact version we cited? It's all here, licensed CC BY 4.0.

Data & provenance

Limitations

- Most of our data comes from a single corpus over a single period. A different corpus could very plausibly give different figures. - Some verification was done by one person alone, with no second reviewer to compare against. Wherever a pass rate appears, there is an uncertainty in it we have not measured. - Our regional-language coverage is currently one dialect variant per language tested. Speakers elsewhere might judge differently, and that has not been tested. - This is not academic work and it has not been peer reviewed. The method is written out in the open precisely so it can be argued with.

Revision history

Published
Last updated