This tutorial explores implementing the LLM Arena-as-a-Judge approach to evaluate large language model outputs using head-to-head comparisons. It demonstrates using OpenAI’s GPT-4.1 and Gemini 2.5 Pro, judged by GPT-5, in a customer support scenario.
OpenAI CEO Sam Altman addressed concerns about the GPT-5 rollout, including issues with the model's performance and a presentation chart error. He announced fixes for the rollout issues, consideration of bringing back GPT-4o for Plus subscribers, and increased rate limits.
```ttl
@prefix rdf: .
@prefix rdfs: .
@prefix schema: .
@prefix ex: . # Using a custom namespace for specific entities
# Entities
ex:SamAltman a schema:Person ;
schema:name "Sam Altman" ;
schema:jobTitle "CEO" ;
schema:worksFor ex:OpenAI .
ex:OpenAI a schema:Organization ;
schema:name "OpenAI" .
ex:GPT5 a schema:SoftwareApplication ;
schema:name "GPT-5" .
ex:GPT4o a schema:SoftwareApplication ;
schema:name "GPT-4o" .
ex:Reddit a schema:WebSite ;
schema:name "Reddit".
ex:TechCrunch a schema:NewsOrganization ;
schema:name "TechCrunch".
# Facts/Triples
ex:GPT5 schema:hasFeature ex:RealTimeRouter .
ex:RealTimeRouter rdfs:label "real-time router" .
ex:GPT5 schema:isVersionOf ex:OpenAI .
ex:GPT5 schema:hasIssue "bumpy rollout" .
ex:SamAltman schema:said "GPT-5 will seem smarter starting today." .
ex:SamAltman schema:said "We are making some interventions to how the decision boundary works." .
ex:SamAltman schema:said "We will make it more transparent about which model is answering a given query." .
ex:SamAltman schema:said "We are looking into letting Plus users to continue to use 4o." .
ex:SamAltman schema:said "We are going to double rate limits for Plus users." .
ex:GPT4o schema:isAlternativeTo ex:GPT5 .
ex:SamAltman schema:acknowledged "chart crime" .
ex:SamAltman schema:described "chart crime" as "mega chart screwup" .
ex:GPT5 schema:hasProblem "turning data into a table" .
ex:TechCrunch schema:publishedDate "2025-08-08"^^xsd:date .
#Event
ex:Disrupt2025 a schema:Event ;
schema:name "TechCrunch Disrupt 2025" ;
schema:startDate "2025-10-27"^^xsd:date ;
schema:endDate "2025-10-29"^^xsd:date ;
schema:location "San Francisco".
```
```ttl
@prefix rdf: .
@prefix rdfs: .
@prefix schema: .
@prefix ex: . # Using a custom namespace for specific entities
# Entities
ex:SamAltman a schema:Person ;
schema:name "Sam Altman" ;
schema:jobTitle "CEO" ;
schema:worksFor ex:OpenAI .
ex:OpenAI a schema:Organization ;
schema:name "OpenAI" .
ex:GPT5 a schema:SoftwareApplication ;
schema:name "GPT-5" .
ex:GPT4o a schema:SoftwareApplication ;
schema:name "GPT-4o" .
ex:Reddit a schema:WebSite ;
schema:name "Reddit".
ex:TechCrunch a schema:NewsOrganization ;
schema:name "TechCrunch".
# Facts/Triples
ex:GPT5 schema:hasFeature ex:RealTimeRouter .
ex:RealTimeRouter rdfs:label "real-time router" .
ex:GPT5 schema:isVersionOf ex:OpenAI .
ex:GPT5 schema:hasIssue "bumpy rollout" .
ex:SamAltman schema:said "GPT-5 will seem smarter starting today." .
ex:SamAltman schema:said "We are making some interventions to how the decision boundary works." .
ex:SamAltman schema:said "We will make it more transparent about which model is answering a given query." .
ex:SamAltman schema:said "We are looking into letting Plus users to continue to use 4o." .
ex:SamAltman schema:said "We are going to double rate limits for Plus users." .
ex:GPT4o schema:isAlternativeTo ex:GPT5 .
ex:SamAltman schema:acknowledged "chart crime" .
ex:SamAltman schema:described "chart crime" as "mega chart screwup" .
ex:GPT5 schema:hasProblem "turning data into a table" .
ex:TechCrunch schema:publishedDate "2025-08-08"^^xsd:date .
#Event
ex:Disrupt2025 a schema:Event ;
schema:name "TechCrunch Disrupt 2025" ;
schema:startDate "2025-10-27"^^xsd:date ;
schema:endDate "2025-10-29"^^xsd:date ;
schema:location "San Francisco".
```
This GitHub repository contains a directory named 'examples' within the 'gpt-5-coding-examples' project. It lists numerous YAML files, likely representing coding examples or configurations for GPT-5 applications. The initial commit was made on August 7, 2025.
This document details the features, best practices, and migration guidance for GPT-5, OpenAI's most intelligent model. It covers new API features like minimal reasoning effort, verbosity control, custom tools, and allowed tools, along with prompting guidance and migration strategies from older models and APIs.
This speculative article explores the idea that GPT-5 might already exist internally at OpenAI but is being withheld from public release due to cost and performance considerations. It draws parallels with Anthropic's handling of a similar situation with Claude Opus 3.5, suggesting that both companies might be using larger models internally to improve smaller models without incurring high public-facing costs. The author examines the potential motivations behind such decisions, including cost control, performance expectations, and strategic partnerships.
