HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
inverse-scaling
prize
AI & Machine Learning2022–2023
inverse-scaling / prize

prize

A prize for finding tasks that cause large language models to show inverse scaling

3Distinct people
3Mentions
0Explicit recommenders
626GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A prize for finding tasks that cause large language models to show inverse scaling

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month3 dated mentions

Observed mentions: 2022-06-27 18:18:45 UTC to 2023-05-26 23:37:56 UTC.

0122022-06-01 00:00:00 UTC to 2022-07-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJun 20222022-07-01 00:00:00 UTC to 2022-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-01 00:00:00 UTC to 2022-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-01 00:00:00 UTC to 2022-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-01 00:00:00 UTC to 2022-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-01 00:00:00 UTC to 2022-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsNov 20222022-12-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2023-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-01 00:00:00 UTC to 2023-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-01 00:00:00 UTC to 2023-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-01 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-01 00:00:00 UTC to 2023-06-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsMay 2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 20222022-06-01 00:00:00 UTC2022-07-01 00:00:00 UTC110
Jul 20222022-07-01 00:00:00 UTC2022-08-01 00:00:00 UTC000
Aug 20222022-08-01 00:00:00 UTC2022-09-01 00:00:00 UTC000
Sep 20222022-09-01 00:00:00 UTC2022-10-01 00:00:00 UTC000
Oct 20222022-10-01 00:00:00 UTC2022-11-01 00:00:00 UTC000
Nov 20222022-11-01 00:00:00 UTC2022-12-01 00:00:00 UTC000
Dec 20222022-12-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
Jan 20232023-01-01 00:00:00 UTC2023-02-01 00:00:00 UTC000
Feb 20232023-02-01 00:00:00 UTC2023-03-01 00:00:00 UTC000
Mar 20232023-03-01 00:00:00 UTC2023-04-01 00:00:00 UTC000
Apr 20232023-04-01 00:00:00 UTC2023-05-01 00:00:00 UTC000
May 20232023-05-01 00:00:00 UTC2023-06-01 00:00:00 UTC211

What Hacker News says

3 sources
Thanks that one is very interesting. I especially like how GPT4 performs worse (zero shot greedy decoding) than ChatGPT on those questions. I wonder have you thought about how it relates to 'inverse scaling' (https://github.com/inverse-scaling/prize)? As I was reading it I was thinking how that kind of 'hallucination' is exactly the problem that beam search (as opposed to greedy decoding) is designed to solve, and I see this was addressed later in the paper - unfortunately you guys didn't have access to it on the API and also no access to other things like log likelihoods. A related question I had, is to decompose the blame for the problems these LLMs were having into two parts: (1) the weaknesses of the model size and data size and architecture caused for example by parallelism tradeoffs versus (2) the inherent problems of greedy token p
Read the rest
rediction. For example I could imagine that even an 'oracular' (kolmogorov or solomonoff or whoever absolute minimum theoretical perplexity) single-token-at-a-time-predictor could have related errors purely as a result of greedy decoding, which would be in no way attributable to any kind of size issue or architectural property or parallelism property of the model. As I guess you already know, the reason is just that 'the most likely next token of the response' isn't necessarily the same as 'the next token of the most likely response'.
In A Logic for Expressing Transformers

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.