Join the conversation

Join the community of Machine Learners and AI enthusiasts.

Sign Up
Banaxi-Tech 
posted an update 10 days ago
Post
2862
We're excited to release BananaMind Base Bench 1.1 A new benchmark for base language models with 350 text-completion examples across seven categories. Models are scored using continuation likelihood and receive an Overall Elo score.
Initial results:
BananaMind-2-Medium: 1034
BananaMind-2-Mini: 974
Supra-50M-Base: 973
Supra-1.5-50M-Base-exp: 948
BananaMind-2-Nano: 910
The official script downloads the gated dataset directly from Hugging Face. The dataset is for benchmarking only and may not be used for model training.
BananaMind/BananaMind-Base-Bench-1.1

I love elo system , Why dont you make a leaderboard specifically for your benchmark ?

·

im already going to do Soon!

Looks interesting, definitely will try it out. mind explaining what this measures?

·

Just Text Completion, you can look at the benchmark yourself, its small

Your card gives away enough to price the scale without the data, so I ran your Elo on a model that does not exist.

A uniform random guesser has p=0.25 on every item by construction, four choices. Feed that into your own formula. point_weight = category_weight * difficulty_weight, expected = 1/(1+10**((item_elo-R)/400)), weighted MLE with the 4-game prior at 1000, item Elo straight off your composition table.

Random guessing scores Overall Elo 805.

That number is stable. I do not know your per-category difficulty split, so I tried two very different allocations that both hit 50 per category and 117/117/116 overall. 805.0 and 804.5. Half a point, so the split does not matter.

805 is worth a line on the leaderboard.

Five of the 46 entries score below it. MicroSupra-1k 768, Atom2.7m 794, DistillSupra-0.2M 794, Supra-Mini-0.1M 796, Supra-Mini-v2-0.1M 804.

Nine of 46, 19.6%, have accuracy inside the 95% interval for chance. On 350 four-way items that interval is 25 +/- 4.54pp, so [20.46, 29.54]. Those nine span Elo 768 to 830, and 62 points reads as ranking.

There is a second sign they are guessing, and it comes from your own numbers. I refit every entry assuming correctness is uniform across items, which is the wrong model for a real LM and the right one for a guesser. The nine chance-band entries land a mean 6.0 Elo from published, signs mixed, 7 above and 2 below. The other 37 land a mean 25.3 Elo high, 37 of 37 in the same direction. Real models have a difficulty gradient. The bottom nine show none.

On resolution. At 48% accuracy one standard error is 2.67pp, about 21 Elo. Your median gap between adjacent ranks is 5 Elo, and 23 of 45 gaps are 5 or less. Most neighbours sit about four times inside one standard error. Your card already says small Elo differences should not be treated as decisive, and the leaderboard is where that sentence is missing.

The weighting also reorders, which I read as intended rather than broken. 22 ordered pairs have the higher-accuracy model ranked lower. Sharpest is Supra-1.6-50M-Instruct-Ultra-exp at 44.00% sitting at 928 while Veyra-30M-Base at 43.71% sits at 951. Two entries at exactly 44.00% get 928 and 949. That is a 21 to 23 Elo effect, the design working, and four times your median rank gap.

Credit where it is due, and it is the reason any of this was checkable. You publish the formula, the per-item Elo table, both weight vectors, the answer-position balance and the test.jsonl SHA-256. That is more than most cards this size publish.

Caveat on my side. The data is gated and I am not on the list, so test.jsonl 403s for me. I could not verify that items carry the item_elo your table implies, and I am not quoting my refit as anyone's score. Every score above is straight off your leaderboard.

Smallest useful change: draw the 805 line on the chart, and grey the entries whose accuracy interval crosses it.

Would you put the null on the axis?

·

The chart has a 805 line?

It does, and it shipped on the 28th. Two days before I asked for it. That one is on me.

The check still bought something. I derived 805 from your published formula, not off your chart. Uniform p=0.25 on every item, point_weight = category_weight * difficulty_weight, weighted MLE with the 4-game prior at 1000, item Elo straight off your composition table. Two different category splits that both sum to 350 gave 805.0 and 804.5. Your script.js carries randomChanceElo = 805 as a bare constant and the README states it without showing the work. Two independent routes to the same number is the strongest thing either of us can say about it.

What is still open is the sentence under the chart, not the line.

"Models above the dashed 805 Elo line exceed random-choice chance."

805 is a point. Chance is an interval. On 350 four-way items the 95% interval on accuracy is 25 +/- 4.54pp, so [20.46, 29.54]. Four entries plot above your line and sit inside that band anyway.

CMA-1M-Mini 27.43% at 812. Ant-5M 25.43% at 825. Photon-2.0-1M 28.57% at 825. Photon-1.0-1M 28.57% at 830.

Above the line, and not shown to have beaten chance. With the five already below it, that is 9 of 46.

The table carries none of it. rankedRows sorts on overall and numbers 1 to 46, so MicroSupra-1k at 768 reads as rank 46, worst model, rather than as under the baseline. The chart is the honest half of the page. The table is the half people screenshot.

Would you put the baseline in the table as a row, or grey the nine?