<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>G-Eval: NLG Evaluation using GPT-4 with Better Human Alignment · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2303.16634/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2303.16634/feed.xml" rel="self" type="application/rss+xml" /><item><title>G-Eval: NLG Evaluation using GPT-4 with Better Human Alignment — mentioned by nimitkalra</title><link>https://news.ycombinator.com/item?id=44075030</link><guid isPermaLink="false">urn:hackerpapers:mention:2303.16634:44075030</guid><pubDate>Fri, 23 May 2025 18:04:48 GMT</pubDate><description>&lt;p&gt;One method to get a better estimate is to extract the token log-probabilities of &amp;quot;YES&amp;quot; and &amp;quot;NO&amp;quot; from the final logits of the LLM and take a weighted sum [1] [2]. If the LLM is calibrated for your task, there should be roughly a ~50% chance of sampling YES (1) and ~50% chance of NO (0) — yielding 0.5. But generally you wouldn&amp;#x27;t use a binary outcome when you can have samples that are 50/50 pass/fail. Better to use a discrete scale of 1..3 or 1..5 and specify exactly what makes a sample a 2/5 vs a 4/5, for example You are correct to question the weaknesses of a panel. This class of methods…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2303.16634/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>G-Eval: NLG Evaluation using GPT-4 with Better Human Alignment — HN submission</title><link>https://news.ycombinator.com/item?id=42293942</link><guid isPermaLink="false">urn:hackerpapers:submission:2303.16634:42293942</guid><pubDate>Mon, 02 Dec 2024 07:36:10 GMT</pubDate><description>&lt;p&gt;Garvata: Observability and Debugging for AI Agent Stack&lt;/p&gt;&lt;p&gt;We are stepping into the era of Multi-Agentic Applications, where these apps rely on the interaction between agents, LLMs, tools, vector databases, and other agents. Developers are spending extensive time debugging inaccurate agent outputs and refining their prompts. In the next five years, SMBs might have hundreds of agents managing workflows, while enterprises could be handling thousands. Our mission is to exponentially enhance developer capabilities and improve agent accuracy. Debugging Multi-Agentic Apps is Challenging: 1. Primary issue: Inaccurate outputs — irrelevant, incorrect, or…&lt;/p&gt;&lt;p&gt;3 points; 1 discussion reply on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2303.16634/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>G-Eval: NLG Evaluation using GPT-4 with Better Human Alignment — mentioned by visarga</title><link>https://news.ycombinator.com/item?id=36541072</link><guid isPermaLink="false">urn:hackerpapers:mention:2303.16634:36541072</guid><pubDate>Fri, 30 Jun 2023 19:44:17 GMT</pubDate><description>&lt;p&gt;&amp;gt; A lot of the AI doomerism comes from folks who do not understand the real complexities in making systems which really can function in a fully autonomous way in an environment which is hostile and dynamic. I agree. Autonomy is hard. But a weaker version of it is possible - self replication in software. An AI model can generate text that can train new models from scratch[1]. They can also generate the model code, explain it, make meaningful changes[2], monitor the training run and evaluate the &amp;quot;child&amp;quot; models[3]. So AI can &amp;quot;pull everything from inside&amp;quot; to make a child, no external materials…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2303.16634/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item></channel></rss>
