← Judged questions

writing-004: both judges

A public question in Writing, battery v1. It starts: “Explain how the internet gets a web page from a faraway computer to your screen, as if talking to a curious 10-year-old. Use one everyday an…” Read the question and every model's answer.

228 models judged; 14 disputed (judges 3 or more points apart). The gap is the distance between the two judges' scores. Models are ordered by that gap, widest first.

Sage-A1.5-Q4_K_M gap 4, disputed

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 8/10

The response stays within the 150–220-word range, explains the page-fetching process for a child, and consistently uses a postal-delivery analogy. It clearly covers requests, routers, packets, transmission, and reassembly. The explanations are accurate enough for the audience, though “data packet” and “routers” receive only brief definitions and the pizza/chef analogy slightly mixes metaphors.

The response gives a clear, child-friendly account of how a browser requests a page, how routers direct small pieces of data, and how the computer reassembles them. Its postal-service analogy is sustained effectively, with concrete images such as letters, addresses, and delivery routes. A minor weakness is that some technical terms, especially “router” and “data packet,” are introduced more than fully explained, and the later pizza analogy adds a second comparison. The simplified claim that pieces use the same paths is also not strictly precise, but it does not substantially undermine the explanation.

Judge B: J-A (anthropic/claude-haiku-5.5) 4/10

The text runs roughly 270 words, about 23% over the 150–220 limit. It also stacks several analogies (postal system, postcard, pizza slices, chef, puzzle) despite the brief asking for one. Two hard constraints are violated, though the prose is clear and child-friendly.

The response explains the request-and-response process in clear, friendly language, using simple images such as the postal system and the router as a postal worker that a ten-year-old could follow. Its main weakness is that it breaks two explicit constraints. The text is roughly 270 words against a 150 to 220 limit, and it introduces at least five analogies where the brief asked for one. The repeated comparisons dilute the single through-line the brief requested.

Codellama 34B Instruct gap 3, disputed

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 7/10

The response is within the 150–220-word requirement, uses a single accessible communication analogy, and avoids unexplained technical jargon. It clearly describes a request going to a website’s computer and information returning to the device. However, the explanation is simplified and omits the intermediate steps that actually move the page across the internet, making it competent but fairly generic.

The response explains the basic request-and-response idea in language suitable for a young child, and the friend-and-game scenario gives the explanation an approachable starting point. Its main weakness is that the analogy and technical account remain broad: the response does not explain that the request travels through multiple connecting computers or that a page may arrive as separate pieces. It also repeats the idea of sending a message without adding much detail about how the screen turns returned information into a webpage. Overall, it fulfills the stated constraints with clear but elementary coverage.

Judge B: J-A (anthropic/claude-haiku-5.5) 4/10

Word count is roughly 175, within the 150-220 range. Uses a friend-game analogy, but the analogy is muddled (drawing a picture or messaging app) and the explanation is vague: no mention of servers, addresses resolving, packets or routing, so the mechanism is not really explained. Ends with a restatement that adds little.

The response meets the length requirement and addresses a young audience with a friendly tone and an everyday analogy. Its main weakness is that the analogy does not map cleanly onto the mechanism: the friend-and-game comparison blurs together drawing a picture and using a messaging app, and the actual steps of how a page travels from a distant server to the screen are described only in general terms. Key ideas such as requests, servers, and data broken into pieces are absent, so the explanation leaves the reader with a loose sense of the process rather than a clear picture of it.

Deepseek V2 16B Lite Chat gap 3, disputed

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 7/10

The response is within the requested length, uses a clear envelope-and-house analogy, explains DNS and the browser in child-friendly terms, and traces the page from request to display. It is somewhat oversimplified and misleadingly suggests a building finds and relays the originating computer, but remains understandable and broadly accurate.

The response clearly walks through the main stages: entering an address, finding the destination, requesting information, and having the browser display it. Its envelope analogy is accessible and consistently tied to the explanation, while technical terms such as DNS server and browser receive brief explanations. The main weakness is that the “big building” description blurs the roles of DNS, web servers, and network routing, making the journey sound more centralized than it is. The treatment of code is also only lightly explained.

Judge B: J-A (anthropic/claude-haiku-5.5) 4/10

The response uses a clear envelope-and-friend analogy and explains DNS in plain terms. However, it runs about 245 words, roughly 12% over the 220-word maximum, beyond tolerance. It also blurs the DNS server with the page's host, calling both 'the big building'.

The response keeps a consistent, child-friendly register and anchors its explanation in one everyday analogy, a note passed across the street. It explains the DNS lookup by comparison with asking a store clerk for directions, which suits a curious 10-year-old. Its main weakness is length: the text runs noticeably past the 150 to 220 word range. It also conflates the DNS server with the server hosting the page, calling both 'the big building', which makes the request-and-response steps harder to follow. The final sentence about the browser assembling the page is clear.

Dolphin Phi 2.7B V2.6 gap 3, disputed

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 6/10

The response is within the requested length, uses an accessible catch-and-slingshot analogy, and explains coding in simple terms. However, it incorrectly presents the destination as a friend's computer and suggests the internet itself is a single slingshot, omitting that pages come from web servers and travel through multiple networks. This weakens the explanation's accuracy.

The response has a clear, child-friendly structure and consistently uses the catch analogy to make distant data transfer imaginable. Its explanation of computers using shared codes is also accessible for the intended audience. The main weakness is conceptual accuracy: it treats a web server as a friend’s computer and describes the internet as one invisible slingshot, rather than explaining that data travels through many connected networks to a server. The result is understandable but substantially oversimplified.

Judge B: J-A (anthropic/claude-haiku-5.5) 3/10

Word count is roughly 230, above the 150-220 range by a margin beyond tolerance. The response uses a catch-and-slingshot analogy, but it mischaracterises the mechanism: the internet is not a slingshot, and it omits packets, addresses, servers and routing. The web page is described as sent as one message, and the secret-code explanation is vague and inaccurate.

The response adopts a child-friendly register and a single extended analogy, which matches the requested audience and keeps the tone consistent. Its main weakness is that the analogy stops explaining the actual process. The internet is described as a big invisible slingshot, and the explanation of how data travels is replaced by a vague secret-code idea with no mention of servers, addresses, or data being split into packets. The word count also appears to exceed the requested 150 to 220 range, a constraint the response does not meet.

Granite Code 3B Instruct gap 3, disputed

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 6/10

The response stays within the requested length, uses one clear library analogy, and avoids unexplained jargon. However, it repeats nearly the same explanation three times and gives little actual account of how a browser requests, receives, and assembles a page, reducing clarity and educational usefulness.

The response’s strength is its accessible library analogy, which makes the basic idea of requesting information from a distant computer understandable to a young reader. It also maintains a friendly tone and appears to fit the requested word range. Its main weakness is substantial repetition: the dinosaur example and summary largely restate the opening paragraphs. More importantly, the explanation leaves out the key steps that turn a request into a visible page, such as the browser contacting the website and receiving page pieces. As a result, it is readable but technically thin.

Judge B: J-A (anthropic/claude-haiku-5.5) 3/10

The response is recognisably an attempt at the requested explanation, but it never says how a page travels: no requests, data pieces, or routing. It repeats the same library paragraph three times, and the closing summary restates the opening verbatim. It also includes an unrequested self-introduction.

The response stays on the requested subject and keeps one everyday analogy, a library and a librarian, which is accessible to a ten-year-old. Its main weakness is that it never explains the actual mechanism. The core sentence, that a computer sends a message to the screen just like a librarian sends a book, is vague and circular. The middle and final paragraphs repeat the opening almost word for word, so the text adds no new information and does not fully deliver the explanation requested.

Lfm2 24B gap 3, disputed

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 7/10

The response is within the 150–220-word range and clearly explains requesting, routing, server retrieval, and browser display. It uses a consistent delivery-and-library analogy and explains terms such as server, router, and browser for a child. The explanation is accurate enough for the audience, though some descriptions are simplified and familiar rather than especially original.

The response succeeds by presenting the process as a delivery journey, with the request as a note, routers as traffic cops, and the server as a digital library. It also defines potentially unfamiliar terms in context and maintains an accessible tone throughout. Its main weakness is that the explanation simplifies networking in ways that can mislead slightly: the returned data need not follow the same route, and a web page usually contains more than a single picture. The overall treatment remains clear and suitable for a curious 10-year-old.

Judge B: J-A (anthropic/claude-haiku-5.5) 4/10

The text is 150-220 words and clearly explains a page request traveling to a server and back. It breaks the one-analogy rule by stacking several: a note to a friend, highways, a library, traffic cops and a puzzle. The opening also muddles the setup by treating the friend's computer as the server.

The response explains the request-and-response cycle in simple, readable sentences that suit a curious ten-year-old. Jargon such as server, router and browser is defined in plain terms, and the length meets the requested range. Its main weakness is the brief's single-analogy requirement, since it moves between a note to a friend, highways, a library, traffic cops and a puzzle. The opening also conflates the friend's computer with the website's server, which blurs the central idea.

Mathstral 7B V0.1 gap 3, disputed

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 7/10

The response is within the requested length, uses one accessible game-and-messenger analogy, and explains the basic request-and-return process without unexplained technical jargon. It is clear and age-appropriate, though repetitive and somewhat imprecise about the roles of the internet, website, and computer.

The response succeeds in making a distant web page understandable through a familiar board-game and messenger comparison. Its short paragraphs and repeated mapping between asking for information and receiving it suit a young audience. However, the explanation simplifies the process so heavily that it blurs important roles: the website is treated almost like a person, while the browser and the steps involved in finding the faraway computer are omitted. The shifting phrasing about who is asking also creates a minor clarity problem.

Judge B: J-A (anthropic/claude-haiku-5.5) 4/10

Word count is roughly 170, within range, and the child-friendly tone holds. However, the single analogy (a friend describing a board game) is muddled: the messenger and game-board roles shift, and the response never explains packets, servers, DNS or how a page is assembled and displayed on screen. It is an attempt at the requested explanation that misses the mechanism.

The response attempts an explanation pitched at a child, using one analogy of a friend describing a board game, and keeps a simple, readable register throughout. Its main weakness is that the analogy shifts meaning mid-way: the internet is first a game room, then a messenger, and the friend's board is conflated with the website. The actual process of requesting a page, sending it in pieces, and rendering it on the screen is never described. The text also ends by restating the analogy rather than clarifying the mechanism, leaving a curious child with little accurate understanding of how the page arrives.

Qwen 0.5B Chat V1.5 gap 3, disputed

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 4/10

The response explains the basic request-and-response idea, but it is highly repetitive, omits the required everyday analogy, uses unexplained technical terms such as “server,” does not meaningfully address a curious 10-year-old, and appears substantially over 220 words.

The response’s main strength is that it identifies the central exchange: a device requests a web page and a server sends information back. However, it fails several explicit constraints. It provides no everyday analogy, leaves “server” and related concepts unexplained, and repeats nearly the same paragraph many times. The repetition makes the explanation difficult to follow and likely pushes it beyond the requested length range. It therefore offers only a basic outline rather than a complete child-friendly explanation of how the page reaches the screen.

Judge B: J-A (anthropic/claude-haiku-5.5) 1/10

The response is a repetitive loop of the same sentence about requests to a server, repeated about a dozen times. It never explains the path of a page to the screen, uses no analogy, is far outside the 150 to 220 word range, and is not aimed at a 10-year-old. The text is readable but the requested explanation is absent.

The response attempts a basic description of a client sending a request to a server and receiving a reply, which is a real if very thin part of the topic. However, the same sentence is repeated many times in a row, so the text is padded and never progresses. It omits the core steps the brief asks for, such as addresses, routing, packets, and rendering on screen. It contains no everyday analogy and does not explain terms for a child. The total length is well above the requested word count, and the piece is not delivered as a child-friendly explanation.

Qwen2.5 Coder 1.5B Instruct gap 3, disputed

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 6/10

The response is within the requested length, uses one toy-based everyday analogy, and avoids unexplained jargon. It gives a basic account of a request and a reply, but it does not clearly explain that a faraway computer (server) stores and sends the page. The analogy is repetitive and technically vague.

The response’s strength is its accessible toy analogy, which makes the idea of sending a request and receiving a web page approachable for a young reader. Its main weakness is that it reduces the internet to an “internet’s toy” and never identifies the faraway computer that actually stores the page. Repetition of the toy comparison also takes space away from explaining the journey between computers, so the result meets the formal constraints but provides only a shallow explanation.

Judge B: J-A (anthropic/claude-haiku-5.5) 3/10

The response is roughly 150 words, meets the child-friendly register and uses a toy analogy, but the explanation is vague and inaccurate: it never mentions servers, addresses, packets, or how the page is requested and split into pieces. It describes messages between toys without the actual mechanism, so the brief's core explanatory task is only partly delivered.

The response adopts a warm, child-appropriate voice and sustains a single toy-based analogy throughout, which fits the brief's audience and its request for one everyday comparison. Its main weakness is that the explanation stays at the level of general messaging and never identifies the actual steps: a request reaching a server, the page being found and broken into pieces, and those pieces being reassembled by the browser. The closing paragraph also repeats the opening idea without adding information, so the answer feels padded rather than explanatory.

Qwen3-4B-Instruct-2507 gap 3, disputed

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 8/10

The response is within the 150–220-word range, uses a sustained everyday messenger-and-drawing analogy, and explains paths, computers, and page pieces in child-friendly language. It clearly describes sending, routing, receiving, and reassembling a web page. The explanation is somewhat simplified and relies on familiar imagery, but it is accurate enough and well targeted.

The response clearly fulfills the brief by explaining a web page as tiny pieces traveling from a distant computer to a screen. Its messenger, roads, delivery-truck, and puzzle imagery gives a 10-year-old several concrete ways to understand the process, while unfamiliar concepts are explained in context. A weakness is that the analogy shifts between messengers, trucks, letters, and puzzles, which makes the underlying mechanism slightly less cohesive. It also simplifies web pages into a single drawing, omitting that pages may include text, images, and interactive code, though that omission is reasonable for the audience.

Judge B: J-A (anthropic/claude-haiku-5.5) 5/10

Word count is roughly 185, within the 150–220 range. Uses one consistent analogy (messenger/drawing) and explains pieces, paths, and reassembly in child-friendly language. However, it is vague on key mechanics (no packets explained, no mention of requests or servers, 'web page' vs 'drawing' mapping is loose) and ends with an emoji, and the 'fastest path' and 'safely' claims are shallow. Constraints are met, so the score reflects clear but flat, imprecise content.

The response meets the length range and sustains a single analogy of a messenger carrying a drawing in pieces, which suits a curious ten-year-old and keeps the register consistent. Its main weakness is imprecision: it never explains what the browser actually requests, what a server is, or how the pieces are labelled so they can be reordered, so the core mechanism stays vague. The closing emoji and repeated 'magical' framing add decoration without adding explanation. The piece reads clearly but offers little that goes beyond the expected picture of the internet as a delivery system.

Qwen3.6-27B gap 3, disputed

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 8/10

The response clearly explains requests, routing, returning data, and assembling a page for a child. Its library and postal-system analogy is sustained and understandable, with technical terms such as “request” explained in context. It appears within the 150–220-word requirement, though the overall analogy is familiar rather than especially original.

The response’s main strength is its clear sequence: it shows a browser sending a request, intermediary computers guiding it, the remote computer returning page pieces, and the screen reassembling them. The library and postal analogy makes the process accessible without relying heavily on unexplained jargon. Its main weakness is that the analogy combines a library, letters, packages, and sorting centers in a somewhat conventional way, so the explanation is more effective than distinctive. A brief explanation of what the browser does would also make one step more precise for younger readers.

Judge B: J-A (anthropic/claude-haiku-5.5) 5/10

The response uses one consistent library-and-postal analogy and explains terms like request and browser clearly for a child. However, my count is roughly 270 words, well above the required 150 to 220, a violation beyond tolerance.

The response builds one coherent analogy, a distant library book sent by letter, and carries it through the whole explanation, which suits a curious 10-year-old. Jargon such as request and browser is explained in plain terms, and the sentences are clear and correct. The main weakness is length: the text runs to roughly 270 words, well beyond the requested 150 to 220 range. The closing paragraph also repeats the idea of distance and helpers somewhat, adding bulk without new content.

Sailor2 1B Chat gap 3, disputed

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 4/10

The response attempts to explain the journey, but it is far longer than the required 150–220 words and uses the “tiny computer” idea repetitively rather than a clear everyday analogy. It leaves terms such as server, cloud, and data largely unexplained, and contains confusing claims that a web page becomes a computer.

The response does provide a recognizable sequence from a remote server to a screen, which shows some engagement with the requested subject. However, it substantially exceeds the word limit and does not deliver a coherent everyday analogy. Repeated descriptions of everything as “tiny” replace explanation rather than making the process clearer for a 10-year-old. Several statements are technically confused, especially the suggestion that the web page becomes a computer or processor. The prose is also highly repetitive, so the individual steps do not build a useful mental model of how a page travels and appears.

Judge B: J-A (anthropic/claude-haiku-5.5) 1/10

The response repeats 'tiny, tiny' dozens of times and never explains the request-response path (DNS, IP, packets, browser rendering). It has no coherent analogy, uses unexplained jargon like 'web server' and 'cloud', and is far outside the 150-220 word range (roughly 400+ words). It fails the brief and is hard to read.

The response attempts a child-friendly explanation with numbered sections, but it fails the brief on substance. Its central analogy of 'tiny' computers is never developed into a mechanism, and the actual steps of sending a page (requests, addresses, data split into pieces, browser display) are not described. The words 'tiny, tiny' recur so often that the text becomes repetitive and hard to follow. The length also substantially exceeds the requested 150 to 220 words. The one partial strength is the friendly opening addressed to a young explorer, which shows some intent toward the audience.

Smollm2 1.7B Instruct gap 3, disputed

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 6/10

The response is 150–220 words, uses an everyday delivery analogy, and explains terms such as “server,” “URL,” and “downloading.” However, its account is technically confused: it says the phone travels to the server and that the picture arrives at the server, rather than explaining the server sending page data to the device.

The response has a child-friendly tone and gives concrete explanations for several unfamiliar terms. Its delivery-box and race-car imagery makes the general idea of remote information transfer approachable. However, the central sequence is inaccurate and repetitive: the phone is described as moving to the server, and the picture appears to arrive at the server even though it was already stored there. It also substitutes a shared dog picture for a fuller explanation of how a browser requests and receives a web page, leaving the main process only partly explained.

Judge B: J-A (anthropic/claude-haiku-5.5) 3/10

Word count is roughly 170, within range. One analogy is used, but the explanation is technically wrong: it says the friend's phone types a URL to fetch a picture from a server, conflating sharing with web page retrieval. It omits requests, responses, DNS, and packets. It fails to explain how a web page reaches the screen, so the content is largely inaccurate.

The response adopts a child-friendly tone and keeps to a single analogy about sending a dog photo, with a plausible length. Its main strength is accessibility of language. Its main weakness is that the mechanism it describes is inaccurate: it treats a URL as a secret code that the friend types to receive a map, and it never explains how a browser requests a page or how the data is split and routed across networks. The core question about getting a web page to the screen is therefore not answered correctly.

YI 6B Chat V1.5 gap 3, disputed

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 6/10

The response is within the requested length, uses a familiar LEGO analogy, and avoids unexplained technical jargon. However, it inaccurately treats a web page as a physical piece or special paper and does not clearly explain the browser, server, data packets, or how the pieces become a page on screen.

The response’s main strength is its accessible LEGO-and-friend analogy, which gives a young reader a simple sense that information travels from a distant place in pieces. Its weakness is that the analogy becomes muddled: a web page is alternately treated as a LEGO piece, a picture fragment, and “special paper,” while the explanation never connects the process to a browser displaying the assembled result. The repeated castle retrieval also oversimplifies the internet’s role and leaves the actual journey from computer to screen unclear.

Judge B: J-A (anthropic/claude-haiku-5.5) 3/10

Word count is roughly 190, within range, and it uses a LEGO analogy as requested. However, the analogy is muddled: the castle is built from pieces fetched by a friend, and the explanation never describes requests, servers, or data packets reaching the screen. The core mechanism is misrepresented, so the piece only partly engages the brief.

The response attempts the requested child-friendly explanation and keeps a single everyday analogy, the LEGO box, with a plain register suited to a 10-year-old. Its length appears to fall within the 150 to 220 word range. Its main weakness is that the analogy breaks down and misrepresents the mechanism. It describes a friend fetching castle pieces from a box, but never explains how a request travels to a distant computer, how the page is split into parts, or how those parts are reassembled on the screen. The result is confusing, and the central process is not clearly conveyed.

Aya Expanse 8B gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 7/10

The response is approximately 180 words, uses a single library analogy, explains cables and wireless signals in child-friendly terms, and avoids unexplained technical jargon. It clearly describes requesting information from a distant computer, though it simplifies the process substantially and does not explain how the page is assembled or displayed.

The response gives a clear, accessible account aimed at a 10-year-old. Its library analogy consistently maps requests, distant computers, and delivered information to familiar objects, while the examples of recipes, cats, stories, and videos make the idea concrete. Its main weakness is that it compresses the process into the internet simply “getting that book”: it does not mention that a web page is requested by a browser, sent in small pieces, and assembled on the screen. The explanation is therefore competent but somewhat generic and technically simplified.

Judge B: J-A (anthropic/claude-haiku-5.5) 5/10

Word count is roughly 200, within 150-220. Uses a single library/librarian analogy and a child-friendly voice. However, the explanation is shallow: it never explains packets, IP addresses, DNS, or the request-response loop, and 'the internet then travels through special roads' is vague. 'Web address' and 'cables' are only loosely explained, and the analogy is stretched by treating computers as books.

The response keeps a consistent, child-friendly voice and holds to one library analogy with a librarian, which suits the brief's request for a single everyday comparison and a length within the 150 to 220 word range. Its main weakness is conceptual vagueness: it describes the internet as travelling along 'special roads' without explaining how a request reaches a faraway computer or how the page is split up and reassembled. The analogy also blurs computers and books, so the mechanism is less clear than the friendly tone suggests. The explanation is accurate in outline but thin on the actual steps.

Codellama 13B Instruct gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 5/10

The response is 171 words and uses child-friendly language, but it introduces several analogies—a phone, a window, and a map—despite the request for one. It also gives only a vague account of delivery, saying the internet “follows the map,” without explaining the computer hosting the page or how information reaches the screen.

The response has a clear, accessible tone and stays within the required 150–220-word range. Its map-and-journey comparison offers a simple way to think about a web address, and the prose is grammatically clean. However, the explanation remains very general: it does not meaningfully describe the faraway computer, the browser, or the steps by which the page travels. It also layers multiple comparisons, including a phone and a window, rather than maintaining one everyday analogy as requested. The result is readable but only partly fulfills the explanatory brief.

Judge B: J-A (anthropic/claude-haiku-5.5) 3/10

Word count is roughly 150-160, within range. However, the response never explains how a page travels: no servers, packets, routing or request/response. It describes a phone analogy and a vague map, which only gestures at the requested mechanism. Clear, child-friendly tone but the core explanation is missing.

The response adopts a warm, child-appropriate voice and keeps its vocabulary simple, meeting the requested register and approximate length. Its main weakness is that it does not explain the actual process: it never mentions a request to a server, data being split and routed across networks, or the page being sent back. The phone-as-internet and map analogies are loose and blur together, so the reader learns that the internet connects distant people but not how a web page arrives on screen. The brief's central question is left largely unanswered.

Codellama 7B Instruct gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 7/10

The response is within the requested length, uses one consistent library analogy, and explains “server” and “downloads” in child-friendly terms. It clearly describes requesting a site and receiving its information. However, it simplifies the process substantially and focuses on the computer rather than explicitly explaining how the page appears on the screen.

The response’s main strength is its accessible library analogy, which gives a 10-year-old an understandable model for a website request, a server, and downloaded information. Its language is clear and its length appears to satisfy the constraint. The main weakness is that it treats the internet as a direct exchange between a computer and server, leaving out the journey through connecting networks and the step where the browser turns received information into a visible page. The “library card” comparison for the computer is also imprecise.

Judge B: J-A (anthropic/claude-haiku-5.5) 5/10

Length is about 200 words and the library analogy is used consistently and kept simple. The explanation is muddled: the internet is called 'a big library', the server is a librarian, and your computer is 'your library card'. It omits how addresses are looked up and how data travels in pieces, so it is not a correct account of the process.

The response meets the length range and sticks to one everyday analogy, a library, which suits a curious 10-year-old and is written in plain, readable sentences. Its main weakness is accuracy. It equates the internet itself with a library and makes the computer 'your library card', which confuses the roles of network, server and client. It also leaves out the address lookup and the way data is split up and routed, so a child would come away with an incomplete and partly wrong picture of how a page reaches the screen.

Deepcoder 14B Preview gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 4/10

The response uses a clear postal-letter analogy and explains the basic request-and-reply process in accessible language. However, it is about 264 words, substantially above the required 150–220 range, and terms such as “browser” are used without explanation. The explanation is also somewhat simplified, but remains understandable for the intended age.

The response’s main strength is its consistent postal-service analogy: envelopes, addresses, delivery, and replies give a 10-year-old an intuitive picture of requesting and receiving a webpage. It also identifies that the returned material includes words and pictures. Its main weakness is failure to meet the stated length limit, at roughly 264 words, along with using “browser” without defining it. The explanation further omits useful intermediate ideas, such as breaking information into smaller pieces, though that omission is less significant than the explicit constraint violations.

Judge B: J-A (anthropic/claude-haiku-5.5) 6/10

Word count is roughly 220-240, near the upper bound of 150-220 but within tolerance. Uses one consistent post-office analogy, explains terms plainly, and is clear for a 10-year-old. The analogy is expected and the text is somewhat generic ('it's like magic', 'voila'). Constraints appear met, so competent band.

The response meets the brief's core demands: it addresses a curious young reader, sustains a single everyday analogy of writing and mailing a letter, and explains the sending, looking up and returning of a webpage in clear language. Its strength is consistent, accessible framing that a child could follow. Its weakness is that the central idea is expected, and phrases such as 'it's like magic' and 'voila' are stock lines that add little. The length also sits at or slightly above the requested upper limit, which a careful reader might notice.

Deepseek Coder 1.3B Instruct gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 3/10

The response is within the requested length and attempts an everyday analogy, but it does not explain the actual journey from a distant computer to the screen. It repeats nearly identical sentences, uses multiple analogies despite the singular constraint, and omits servers, addresses, data transfer, and displaying the page.

The response does recognize that requesting a web page involves asking another computer or place for information, and its language is simple enough for a young reader. However, it never provides a usable explanation of the process: the repeated hide-and-seek and library comparisons remain vague, and several paragraphs restate the same claim. It also introduces more than one analogy when the task requested one. As a result, the piece is a partial attempt rather than a complete, informative explanation.

Judge B: J-A (anthropic/claude-haiku-5.5) 1/10

The response is repetitive and never explains how a web page travels across the internet: no requests, servers, packets, or routing appear. It repeats the same 'This is similar to how the internet works' sentence and duplicates a paragraph verbatim. The hide-and-seek and library analogies are muddled and do not describe the mechanism. Word count is roughly 120, below the 150 to 220 range.

The response opens with a playful framing and attempts an everyday analogy, which fits the requested child-friendly register. However, it never describes the actual mechanism of delivering a web page, such as a request sent to a server and data returned in pieces. Its main weakness is repetition: the same sentence and one paragraph recur several times, and the hide-and-seek and library comparisons do not clarify the process. The text also falls short of the required length range.

Deepseek Coder 6.7B Instruct gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 6/10

The response is within the requested length, uses one playground analogy, and explains server, client, and URL terms. However, the analogy becomes confusing and technically inaccurate: it treats the webpage as a toy car, then says the server moves to the webpage and sends the server back. Repetition also weakens the explanation.

The response makes a clear attempt to explain web-page delivery for a child, using a single playground-and-toy-car analogy and briefly defining terms such as server, client, and URL. Its main weakness is that the analogy assigns inconsistent roles: the toy car alternates between representing the page and the server, while the server is described as moving to the page and then being sent back. This obscures the actual request-and-response process. The prose is readable and appears to satisfy the length requirement, but the explanation would benefit from a more coherent analogy and less repetition.

Judge B: J-A (anthropic/claude-haiku-5.5) 4/10

Word count is roughly 240, above the 150-220 range by more than 10%, a hard-constraint violation. The analogy is muddled: the toy car is simultaneously the server and the web page, and the wizard is the internet, so the mapping is confused. The explanation of what actually happens (requests, responses, data sent back) is inaccurate, with the server moving to the toy box and being sent back to pick up.

The response adopts a playful child-friendly voice and attempts a single extended analogy, which fits the requested audience. However, the analogy breaks down quickly: the toy car is assigned to both the server and the web page, and the internet is cast as a wizard who sends messages, so a 10-year-old would be left with a confused picture. The text also runs noticeably past the requested 150 to 220 words, and the closing line adds an unrequested pleasantry. The core mechanism of request and response is only loosely conveyed.

DeepSeek-R1-Distill-Qwen-14B gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 5/10

The response gives a complete 150–220-word explanation and uses a consistent librarian-and-book analogy. However, it leaves several terms unexplained, including “server,” “router,” and “IP addresses,” despite the explicit requirement to avoid unexplained jargon. Its numbered, meta-commentary format is also less natural for a curious 10-year-old.

The response’s main strength is its clear sequence: finding the address, making a connection, fetching the page, and displaying it. The librarian analogy gives the explanation an accessible organizing image. Its main weakness is that it assumes rather than explains important technical vocabulary, especially server, router, and IP address. The opening discussion of “understanding the request” also sounds like process commentary instead of child-focused teaching. The result is understandable in outline but does not fully satisfy the requested audience and explanation constraint.

Judge B: J-A (anthropic/claude-haiku-5.5) 3/10

Word count is roughly 150-170, within range, and one librarian analogy is used. However, the response opens with 'Alright, let's break it down step by step' and uses a numbered list with bold headers, not a conversation with a 10-year-old. Jargon like DNS, IP addresses and router is named but not explained, and the explanation is thin on how data travels.

The response uses a single everyday analogy, a librarian fetching a book, which is a reasonable choice for a young audience and is applied consistently across the steps. Its main weakness is register: it reads as a technical outline with bold headings and a numbered list rather than a conversational explanation to a curious ten-year-old. Terms such as DNS, IP addresses and router appear without adequate explanation, breaking the brief's requirement that jargon be explained. The explanation of how data is split and routed across the network is also missing, so the piece only partly delivers the requested account.

dolphin-2.9.1-yi-1.5-34b gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 7/10

The response is within the 150–220-word range and clearly explains the process for a 10-year-old using a sustained house-and-toy analogy. It defines URL and web browser rather than leaving them unexplained. The explanation is somewhat simplified and slightly muddles the analogy, especially by suggesting the faraway computer must agree before sending the page.

The response clearly presents the main sequence: identifying an address, sending a request, receiving page information, and having a browser display it. Its house, friend, and toy comparison gives a young reader an accessible mental model, and the technical terms URL and web browser are explained. However, the analogy shifts between houses, knocking, toys, and a toy box, which makes it less coherent than it could be. The claim that the remote computer “agrees” also oversimplifies how ordinary web requests work, though this does not prevent the overall explanation from being understandable.

Judge B: J-A (anthropic/claude-haiku-5.5) 5/10

The response stays in a child-friendly voice and explains URL, request, and browser steps. However, it mixes several analogies (neighborhood, friend's toy, knocking, toy box) despite the brief asking for one. Word count is about 220, borderline but within tolerance.

The response uses a consistent child-friendly voice and explains the core flow of a request, response, and browser rendering in plain language. It defines URL in parentheses, meeting the jargon requirement. Its main weakness is that it blends several analogies, a neighborhood, a borrowed toy, knocking on a door, and a toy box, rather than sustaining the single everyday analogy the brief requested. It also omits how the address is resolved to a machine and how data is split into pieces, so the explanation is simplified to the point of being incomplete.

Falcon2 11B gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 7/10

The response explains the basic request-and-return path using a single library analogy, defines its simplified terms, and stays accessible to a 10-year-old. It appears slightly under 150 words, but within the rubric’s approximate 10% tolerance. The explanation is clear and correct at a high level, though it omits useful details such as the browser, packets, and how the page appears on screen.

The response’s main strength is its sustained library analogy: the librarian and book-location steps make the exchange between a device and a distant computer easy to follow. Its weakness is that the analogy simplifies several important stages too heavily, presenting the internet mainly as a lookup followed by a direct return. It also does not explain the browser’s role or how received page information becomes the visible page. The language remains clean, age-appropriate, and within the requested approximate length.

Judge B: J-A (anthropic/claude-haiku-5.5) 5/10

Word count is roughly 150-160, within the 150-220 range. Uses one library analogy, explains requests and responses for a child. However, the analogy is muddled: the librarian is described as a computer and the library as the internet, and the book 'location' concept is loose. It omits DNS, IP addresses, packets and routing, so the explanation of how the page actually travels is thin.

The response meets the length requirement and sustains a single library analogy suited to a young reader, with plain sentences and no unexplained jargon. Its main strength is accessibility. Its main weakness is conceptual confusion: it calls the library the internet and the librarian a computer, blurring which part does the looking up and which does the sending. The step where the web page travels back through intermediaries is also oversimplified, leaving out how addresses and data pieces move across networks. The explanation is clear enough for a child but less accurate than the brief's goal of a faithful explanation would require.

Flint 40B A2B gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 8/10

The response is within the 150–220-word range, addresses a 10-year-old clearly, uses an everyday mail and jigsaw-puzzle analogy, and explains “server” and “packets” in accessible terms. It is accurate at an introductory level and has a friendly, coherent voice, though it omits some intermediate steps such as finding the server’s address.

The response gives a clear, age-appropriate account of requesting a page, sending data through networks, receiving packets, and assembling them on the computer. Its mail-system and jigsaw-puzzle comparisons make the process easy to picture, while the definitions of “server” and “packets” avoid unexplained jargon. The main weakness is that it compresses several important steps into a simple server exchange, leaving out how the website address is located and how the browser turns received information into a complete page. These omissions are acceptable for the requested audience but limit technical detail.

Judge B: J-A (anthropic/claude-haiku-5.5) 6/10

Meets the 150-220 word range (about 185 words) and explains the request, server, and packet reply in child-friendly language, with the server explained. However, it leans on several comparisons (mail letter, paper airplane, library, jigsaw puzzle) where the brief asked for one analogy. The writing is clear and correct but fairly conventional.

The response stays within the requested length and keeps a friendly, curious-child register throughout. It explains the server in plain words and makes the request-and-reply cycle easy to follow. Its main weakness is the brief's single-analogy requirement: the mail-and-letter comparison is joined by a paper airplane, a library, and a jigsaw puzzle, which dilutes the central image. The explanation of packets is also brief, so the idea of data being split and reassembled is only loosely clarified for a young reader.

Gemma 7B Instruct V1.1 gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 7/10

The response is 147 words, within the allowed tolerance for the 150–220-word range, and uses a consistent notebook-and-delivery analogy. It is clear and child-friendly, with no unexplained technical jargon. The explanation is somewhat simplified and omits useful steps such as the browser and intermediate network devices, but it fulfills the brief.

The response’s main strength is its accessible analogy: the faraway computer becomes a friend’s notebook, while the internet becomes a delivery service, making the basic request-and-display process easy to follow. Its weakness is that the analogy compresses several distinct parts of web communication into a messenger, backpack, and notebook, and it does not explain what the browser does. The wording is clean and appropriately directed at a 10-year-old, though the explanation remains fairly generic rather than especially vivid or technically informative.

Judge B: J-A (anthropic/claude-haiku-5.5) 5/10

Word count is roughly 150-160, within range. One analogy (friend, notebook, messenger, delivery) is used consistently and suits a 10-year-old. However, the analogy is mixed: the notebook is first the web page then the screen, and the 'your computer is the messenger' and 'your screen is the notebook' mappings muddle the roles. Jargon like 'request' and 'data' is loosely explained. Clear and competent overall, but not distinctive.

The response uses a single, accessible analogy of a friend sending stories through a delivery service, which suits a curious child and keeps the sequence easy to follow. Its length falls within the requested range and no technical terms are left unexplained in a confusing way. The main weakness is that the analogy's roles shift: the notebook stands for the web page in one step and for the screen in another, and the messenger is assigned to the user's computer rather than to the request itself. This blurs the mapping. The closing summary restates the point without adding new insight, and the prose is generic rather than vivid.

gemma-4-26B-A4B-it gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 8/10

The response is approximately 180 words, uses a consistent warehouse-and-delivery analogy, explains server, IP address, router, and packets, and directly addresses the journey to the screen. It is clear and age-appropriate. The description slightly oversimplifies delivery by implying the server itself breaks the page into packets and omits the browser’s role in rendering the returned content.

The response clearly explains the basic journey from a typed website address to a visible page, using a familiar warehouse and delivery analogy that is accessible to a 10-year-old. It also defines potentially unfamiliar terms rather than leaving them unexplained, and it stays within the requested length. Its main weakness is technical simplification: it presents the server as breaking the webpage into packets and says the pieces reassemble on the screen, without explaining that the browser interprets and displays the returned files. This does not substantially undermine the explanation’s usefulness.

Judge B: J-A (anthropic/claude-haiku-5.5) 6/10

Word count is roughly 205, within the 150 to 220 range. Uses one consistent analogy (warehouse and delivery) and explains server, IP address, router and packet in plain terms. Tone suits a 10-year-old. Some phrasing is generic, such as 'faster than you can blink', and the 'packets as LEGO bricks' extension is slightly strained, so it is competent rather than distinctive.

The response meets the brief's hard constraints: it stays within the requested word range, keeps one analogy, a warehouse and delivery service, running throughout, and defines each technical term such as server, IP address, router and packet as it appears. Its strength is the consistent analogy and the clear, child-friendly sequence from request to delivery. Its weakness is that the LEGO extension of the packet metaphor is strained, and phrases like 'faster than you can blink' are stock expressions. The explanation is accurate at a high level but skips how packets are reassembled in order, and the prose is competent rather than distinctive.

Gemma2 2B Instruct gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 4/10

The response is clear, child-friendly, and approximately 157 words, within the required range. It explains packets and servers using a postal analogy, but introduces a second analogy (“relay race”), despite the request for one. It also leaves “browser” and “routers” insufficiently explained, violating the no-unexplained-jargon constraint.

The response gives a coherent account of a browser request reaching a server and returning data, and its postal comparison is accessible to a 10-year-old. Its main weakness is constraint compliance: it adds a relay-race comparison after already establishing the postal analogy, and terms such as “browser” and “routers” are not clearly defined. The explanation is therefore understandable overall but does not fully satisfy the instruction to use one analogy and explain every technical term.

Judge B: J-A (anthropic/claude-haiku-5.5) 6/10

Word count is roughly 150-170, within the 150-220 range. Uses one postal analogy consistently, explains packets, routers, server and request in simple terms, addresses a child-level reader. Meets constraints; writing is clear but plain and somewhat generic, with a second relay-race comparison added and no real fresh image.

The response meets the stated length range and sustains a single postal-mail analogy that suits a curious ten-year-old, explaining the request, server, and return of data in plain language. Its main strength is clarity and a coherent throughline. Its weakness is that the explanation stays fairly generic: the postal comparison is familiar, and the closing relay-race line introduces a second analogy without developing it. Terms such as packets, routers, and server are defined briefly, though the explanation of how packets are routed and reassembled is absent, leaving the mechanism somewhat thin.

Granite4 350M H gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 2/10

The response acknowledges the requested topic but provides no explanation of how a web page travels to the screen. It omits the required everyday analogy, explanations of concepts, and the 150–220-word length.

The response’s only strength is that it identifies the general subject and uses a clear, grammatical sentence addressed in a friendly way. Its central weakness is that it does not deliver the requested explanation: it contains no analogy, no accessible account of the process, and only a brief promise to explain. At roughly thirty words or fewer, it also falls far below the required length. The response therefore shows minimal engagement with the brief rather than presenting a usable answer.

Judge B: J-A (anthropic/claude-haiku-5.5) 0/10

The response is a single sentence that promises an explanation but never gives one. It contains no analogy, no explanation of web page delivery, and is far short of the 150 to 220 word requirement. It is effectively empty of usable text for this brief.

The response opens with a polite acknowledgement of the request and states willingness to explain how a web page reaches a screen. It then stops, delivering none of the requested content: no description of requests, servers, packets or displaying the page, no analogy and no child-friendly explanation. The only readable element is the commitment to answer, which does not satisfy the brief. The text also adds an unnecessary aside about the assistant's role, which does not contribute to the task. As delivered, the output provides nothing a curious ten-year-old could learn from and does not approach the specified length range.

Granite4 3B gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 7/10

The response is within the requested length, uses one consistent telephone-game analogy, and explains “server” as a faraway computer storing web-page information. It is clear and age-appropriate. However, it simplifies the process substantially, omitting how the browser assembles and displays the returned page and making the telephone comparison somewhat imprecise.

The response clearly presents the basic request-and-response journey using a familiar telephone-game analogy. It defines the server in accessible language and mentions both cables and wireless transmission, which helps a child understand that information travels over distance. Its main weakness is technical incompleteness: it does not explain the browser’s role in turning the returned information into a visible page, nor does it clarify that the server sends page data rather than simply describing what to show. The analogy also repeats the “last friend” comparison more than necessary.

Judge B: J-A (anthropic/claude-haiku-5.5) 5/10

Word count is roughly 190, within the 150-220 range. The single everyday analogy (telephone) is used and explained, and the audience is suitable. However, the analogy is misleading: the telephone game is a one-way relay that garbles messages, not a request-response exchange with a server, and the response conflates the last friend with the server. The explanation omits packets, routing, and DNS, and the closing sentence is loose. Clarity is adequate but the core mechanism is inaccurately depicted.

The response keeps to a child-friendly register and uses one everyday analogy, the telephone game, which is explained in plain language. The length falls within the requested range and no unexplained jargon appears. Its main weakness is that the analogy does not map well onto the mechanism: the telephone game is a chain of whispers passing a message along, whereas a web request is a question sent to a server that replies directly. The server is compared to the last friend, which blurs the request and response steps. The explanation of how data is split and routed across the network is absent, so the child would not learn how the page actually reaches the screen.

Hermes-3-Llama-3.1-8B gap 2

Judged by J-O + J-A.

Judge A: J-O (openai/gpt-5.6-luna) 7/10

The response is within the requested length, uses one sustained letter-and-post analogy, and explains DNS, packets, routers, and switches in child-accessible terms. It clearly traces a request and response from browser to server and screen. The description that computers “agree on a time and place to meet” and that packets use the same roads is somewhat technically misleading, limiting it to competent rather than highly accurate.

The response has a clear structure and a relatable postal analogy that helps a child follow the journey from entering a web address to seeing a page. It also introduces technical terms with immediate explanations, including DNS and packets. Its main weakness is that some analogy details distort the process: computers do not arrange a meeting time and place in the stated sense, and returning data does not necessarily use the same network path. The explanation remains understandable and substantially fulfills the brief, but greater technical precision would improve it.

Judge B: J-A (anthropic/claude-haiku-5.5) 5/10

Word count is roughly 225 words, slightly above the 150-220 range but within tolerance. The postal analogy is used consistently and explains the process for a child. However, the response contains technical inaccuracies: it says DNS 'finds the address' and the computers 'agree on a time and place to meet', and describes a packet as a 'big truck', which muddles the concept. The jargon (router, switch, packet) is only loosely explained.

The response uses a single, consistent postal analogy that suits a curious ten-year-old and follows the requested register. Its main strength is that the analogy carries the overall flow from request to delivery in a readable way. Its main weakness is conceptual accuracy: the packet is described as a truck and the computers are said to agree on a meeting time and place, which misrepresents how the connection works. Terms such as routers and switches are named but only vaguely explained, and the text runs close to the upper word limit.

The other 198 models

Their judges were closer together. Their scores are listed here; open the model's page for the full answer.

ModelJudgesJudge AJudge BGap
Hermes3 3B Llama3.2 J-O + J-A 6 4 2
Internlm2 7B Chat V2.5 J-O + J-A 6 4 2
Lfm2.5 8B A1B J-O + J-A 3 1 2
Lfm2.5 Thinking 1.2B J-O + J-A 6 4 2
Llama-2-7b-chat-hf J-O + J-A 5 3 2
Llama3.2 1B Instruct J-O + J-A 7 5 2
Magistral Small (2506) J-O + J-A 7 5 2
Medgemma1.5 4B IT J-O + J-A 7 5 2
Ministral 3 14B Instruct (2512) J-O + J-A 7 5 2
Mistral Small3.1 24B Instruct 2503 J-O + J-A 8 6 2
Mistral-7B-Instruct-v0.2 J-O + J-A 7 5 2
Mixtral 8x7B Instruct V0.1 J-O + J-A 4 6 2
Nemotron 3.5 Bolt E4B J-O + J-A 8 6 2
NVIDIA Nemotron 3 Nano 30B-A3B J-O + J-A 5 7 2
Olmo2 13B 1124 Instruct J-O + J-A 8 6 2
Opencoder 1.5B Instruct J-O + J-A 4 2 2
Phi-4-mini-instruct J-O + J-A 4 6 2
Qwen 1.8B Chat V1.5 J-O + J-A 2 0 2
Qwen2 Math 1.5B Instruct J-O + J-A 3 1 2
Qwen2 Math 7B Instruct J-O + J-A 5 3 2
Qwen2.5 1.5B Instruct J-O + J-A 6 4 2
Qwen2.5-Coder-3B-Instruct J-O + J-A 7 5 2
Qwen2.5-Coder-7B-Instruct J-O + J-A 6 4 2
Qwen2.5-VL-3B-Instruct J-O + J-A 6 4 2
Qwen3 0.6B J-O + J-A 3 1 2
Qwen3 VL 2B Thinking J-O + J-A 6 4 2
Qwen3-30B-A3B-Instruct-2507 J-O + J-A 7 5 2
Qwen3-4B-Thinking-2507 J-O + J-A 6 4 2
Qwen3-Coder-30B-A3B-Instruct J-O + J-A 5 7 2
Qwen3-Coder-Next J-O + J-A 9 7 2
Qwen3-VL-32B-Instruct J-O + J-A 5 7 2
Qwen3-VL-4B-Instruct J-O + J-A 7 5 2
Qwen3.5-27B J-O + J-A 8 6 2
Qwen3.5-9B J-O + J-A 8 6 2
Sailor2 8B Chat J-O + J-A 7 5 2
Smollm2 360M Instruct J-O + J-A 6 4 2
Solar 10.7B Instruct V1 J-O + J-A 7 5 2
Stable Code 3B Instruct J-O + J-A 4 2 2
Stablelm2 1.6B Chat J-O + J-A 4 2 2
YI 9B Chat V1.5 J-O + J-A 7 5 2
YI Coder 1.5B Chat J-O + J-A 4 2 2
Apertus-8B-Instruct-2509 J-O + J-A 6 5 1
Aya Expanse 32B J-O + J-A 7 6 1
Codegeex4 9B All J-O + J-A 5 4 1
Codegemma 7B Instruct V1.1 J-O + J-A 5 4 1
Codeqwen 7B Chat V1.5 J-O + J-A 3 2 1
Codestral 22B V0.1 J-O + J-A 7 6 1
Cogito 8B V1 Preview Llama J-O + J-A 7 6 1
Command R 35B 08 2024 J-O + J-A 7 6 1
Command R7B (12-2024) J-O + J-A 7 6 1
Command R7B Arabic 7B 02 2025 J-O + J-A 7 6 1
Deepscaler 1.5B Preview J-O + J-A 4 3 1
Deepseek Llm 7B Chat J-O + J-A 7 6 1
Deepseek R1 1.5B Qwen Distill J-O + J-A 3 2 1
Deepseek R1 8B Llama Distill J-O + J-A 5 4 1
DeepSeek-R1-Distill-Qwen-32B J-O + J-A 7 6 1
Devstral Small 2 24B Instruct (2512) J-O + J-A 7 6 1
Exaone Deep 2.4B J-O + J-A 5 4 1
Exaone Deep 7.8B J-O + J-A 7 6 1
EXAONE-3.5-7.8B-Instruct J-O + J-A 5 6 1
Exaone3.5 2.4B Instruct J-O + J-A 5 6 1
Exaone3.5 32B Instruct J-O + J-A 5 6 1
Falcon3 10B Instruct J-O + J-A 7 6 1
Falcon3 1B Instruct J-O + J-A 5 4 1
Falcon3 3B Instruct J-O + J-A 7 6 1
Falcon3 7B Instruct J-O + J-A 5 4 1
Gemma 3n E4B IT J-O + J-A 7 6 1
Gemma 4 12B IT J-O + J-A 8 7 1
gemma-2-9b-it J-O + J-A 7 6 1
gemma-3-12b-it J-O + J-A 7 6 1
gemma-3-27b-it J-O + J-A 8 7 1
gemma-3-4b-it J-O + J-A 5 6 1
gemma-4-31B-it J-O + J-A 8 7 1
Gemma2 27B Instruct J-O + J-A 5 6 1
Gemma3 1B IT J-O + J-A 5 6 1
Gemma3n E2B IT J-O + J-A 7 6 1
Gemma4 E2B IT J-O + J-A 7 6 1
GLM-4.7-Flash J-O + J-A 5 6 1
gpt-oss-120b J-A + J-D 6 7 1
gpt-oss-20b J-A + J-D 6 7 1
Granite Code 8B Instruct J-O + J-A 6 5 1
granite-4.1-3b J-O + J-A 7 6 1
Granite3 Dense 2B Instruct J-O + J-A 4 5 1
Granite3 Dense 8B Instruct J-O + J-A 5 6 1
Granite3.1 Dense 8B Instruct J-O + J-A 7 6 1
Granite3.1 Moe 1B Instruct J-O + J-A 4 3 1
Granite3.2 2B Instruct J-O + J-A 7 6 1
Granite3.3 8B J-O + J-A 7 6 1
Granite4 1B H J-O + J-A 7 6 1
Granite4 Small H J-O + J-A 7 6 1
Granite4.2 3B J-O + J-A 5 4 1
Internlm2 1.8B Chat V2.5 J-O + J-A 3 2 1
Laguna XS 2.1 J-O + J-A 7 6 1
Lfm3 VL 2B J-O + J-A 7 6 1
Llama 4 Scout 17B-16E Instruct J-O + J-A 5 6 1
Llama-3.1-8B-Instruct J-O + J-A 7 6 1
Llama-3.2-3B-Instruct J-O + J-A 6 5 1
Llama-3.3-70B-Instruct J-O + J-A 7 6 1
Llama2 13B Chat J-O + J-A 7 6 1
Marco O1 7B J-O + J-A 5 6 1
medgemma-4b-it J-O + J-A 7 6 1
Meta-Llama-3-8B-Instruct J-O + J-A 7 6 1
Ministral 3 3B Instruct 2512 J-O + J-A 6 5 1
Mistral 7B Instruct V0.3 J-O + J-A 7 6 1
Mistral Nemo 12B Instruct 2407 J-O + J-A 5 6 1
Mistral Small 22B Instruct 2409 J-O + J-A 7 6 1
Mistral Small 24B Instruct 2501 J-O + J-A 7 6 1
Mistral Small 3.2 24B Instruct (2506) J-O + J-A 5 6 1
Nanbeige_Nanbeige4.3-33B J-O + J-A 8 7 1
Nemotron 3.5 Lightning 30B A3B J-O + J-A 6 5 1
Nemotron Mini 4B Instruct J-O + J-A 5 4 1
Olmo-3-7B-Instruct J-O + J-A 5 6 1
Openthinker 7B V2 J-O + J-A 5 4 1
Ornith-1.5-9B J-O + J-A 7 6 1
Phi 2.7B Chat V2 J-O + J-A 5 6 1
Phi-3-mini-4k-instruct J-O + J-A 7 6 1
Phi-3.5-mini-instruct J-O + J-A 5 6 1
phi-4 J-O + J-A 7 6 1
Phi3 14B Medium 128K Instruct J-O + J-A 7 6 1
Qwen 14B Chat V1.5 J-O + J-A 5 4 1
Qwen 4B Chat V1.5 J-O + J-A 5 4 1
Qwen 7B Chat V1.5 J-O + J-A 5 4 1
Qwen2 0.5B Instruct J-O + J-A 3 2 1
Qwen2 1.5B Instruct J-O + J-A 3 2 1
Qwen2.5 Coder 0.5B Instruct J-O + J-A 1 0 1
Qwen2.5-14B-Instruct J-O + J-A 7 6 1
Qwen2.5-32B-Instruct J-O + J-A 7 6 1
Qwen2.5-3B-Instruct J-O + J-A 7 6 1
Qwen2.5-7B-Instruct J-O + J-A 7 6 1
Qwen2.5-Coder-32B-Instruct J-O + J-A 7 6 1
Qwen2.5-VL-7B-Instruct J-O + J-A 7 6 1
Qwen3 1.7B J-O + J-A 6 5 1
Qwen3 VL 2B Instruct J-O + J-A 5 4 1
Qwen3-14B J-O + J-A 7 6 1
Qwen3-30B-A3B J-O + J-A 7 6 1
Qwen3-32B J-O + J-A 7 6 1
Qwen3-4B J-O + J-A 7 6 1
Qwen3-8B J-O + J-A 7 6 1
Qwen3.5-35B-A3B J-O + J-A 8 7 1
Qwen3.5-4B J-O + J-A 8 7 1
Smallthinker 3B Preview J-O + J-A 5 4 1
Smollm2 135M Instruct J-O + J-A 1 0 1
SmolLM3-3B J-O + J-A 7 6 1
Spark-X2.6-4B J-O + J-A 7 6 1
Stablelm Zephyr 3B J-O + J-A 5 4 1
Translategemma 12B IT J-O + J-A 7 6 1
Tulu3 8B J-O + J-A 7 6 1
YI 34B Chat V1.5 J-O + J-A 7 6 1
YI Coder 9B Chat J-O + J-A 5 6 1
Aya 8B 23 J-O + J-A 4 4 0
Codegemma 2B Code V1.1 J-O + J-A 0 0 0
Cogito 14B V1 Preview Qwen J-O + J-A 7 7 0
Cogito 3B V1 Preview Llama J-O + J-A 7 7 0
Deepcoder 1.5B Preview J-O + J-A 3 3 0
Deepseek Coder 33B Instruct J-O + J-A 4 4 0
DeepSeek-Coder-V2-Lite-Instruct J-O + J-A 4 4 0
DeepSeek-R1-0528-Qwen3-8B J-O + J-A 7 7 0
DeepSeek-R1-Distill-Qwen-7B J-O + J-A 5 5 0
Devstral 24B Small 2505 J-O + J-A 7 7 0
Gemma 2B Instruct V1.1 J-O + J-A 5 5 0
Gemma4 E4B IT J-O + J-A 7 7 0
GLM-4.5-Air J-O + J-A 7 7 0
Glm4 9B Chat J-O + J-A 5 5 0
Granite3 Moe 1B Instruct J-O + J-A 4 4 0
Granite3 Moe 3B Instruct J-O + J-A 4 4 0
Granite3.1 Dense 2B Instruct J-O + J-A 5 5 0
Granite3.1 Moe 3B Instruct J-O + J-A 5 5 0
Granite3.2 8B Instruct J-O + J-A 5 5 0
Granite3.3 2B J-O + J-A 6 6 0
Granite4 Micro H J-O + J-A 7 7 0
Granite4 Tiny H J-O + J-A 5 5 0
Granite4.1 30B J-O + J-A 7 7 0
Granite4.1 8B J-O + J-A 7 7 0
Granite4.2 30B J-O + J-A 7 7 0
Granite4.2 8B J-O + J-A 7 7 0
Lfm3 1.7B J-O + J-A 7 7 0
Medgemma 27B IT J-O + J-A 7 7 0
Ministral 3 8B Instruct 2512 J-O + J-A 7 7 0
Muse Glimmer 30B J-O + J-A 7 7 0
Nemotron Cascade 2 30B A3B J-O + J-A 6 6 0
Nemotron3 33B J-O + J-A 7 7 0
Olmo 3.1 32B Instruct J-O + J-A 7 7 0
Olmo-3-7B-Think J-O + J-A 0 0 0
Olmo2 7B 1124 Instruct J-O + J-A 5 5 0
Ornith 9B J-O + J-A 7 7 0
Phi3 3.8B Mini 128K Instruct J-O + J-A 4 4 0
Phi4 Mini Reasoning 3.8B J-O + J-A 4 4 0
Qwen2-VL-7B-Instruct J-O + J-A 6 6 0
Qwen2.5 0.5B Instruct J-O + J-A 3 3 0
Qwen2.5-Coder-14B-Instruct J-O + J-A 7 7 0
Qwen2.5-VL-32B-Instruct J-O + J-A 7 7 0
Qwen3-VL-30B-A3B-Instruct J-O + J-A 7 7 0
Qwen3-VL-8B-Instruct J-O + J-A 5 5 0
Qwen3.5 2B J-O + J-A 4 4 0
Qwen3.6-35B-A3B J-O + J-A 5 5 0
Qwen3.8-27B J-O + J-A 5 5 0
QwQ 32B J-O + J-A 8 8 0
Stablelm2 12B Chat J-O + J-A 5 5 0

Withheld

These models are kept out of the ranking, so none of their scores or reasons are shown:

The judge room names the judges and shows where they disagree most.