GLM-5.3 is live. Run Z.ai's latest model on Friendli Model APIs. Try it today ➜
gspeter0
Available on FriendliAI
Run this model inference on single tenant GPU with unmatched speed and reliability at scale.
Run this model inference with full control and performance in your environment.
Model Details
Model Provider
gspeter0
Model Tree
Input Modalities
Output Modalities
Supported Functionality
text
=== Test 1: Sample 1: Heavy disfluencies, repetitions, and grammar errors ===Raw Input:"so basically uh the the projt dedline is next mondy. rght?but like... we we haven't even got the feedback from theclient yet and i'm like super worried we gonna miss it.um, can you check with john?" Corrected:"So basically, the project deadline is next Monday. Right?But like... we haven't even got the feedback from theclient yet, and I'm like super worried we're gonna miss it.Can you check with John?" -------------------------------------------------------------------------------- === Test 2: Sample 2: Highly technical, microphone noise, lack of punctuation, and phonetic spelling ===Raw Input:"ok so the database connection string is like totally broken. bzz. we are getting connection timeout errors on port fivefour three two and i think the host name shouldbe db dot internal dot local instead of localhost rght?pls check the yaml config immediately" Corrected:"The database connection string is like totally broken. We are getting connection timeout errors on port five four three two and I think the host nameshould be `db.internal.local` instead of `localhost`, right? Please check the YAML config immediately." -------------------------------------------------------------------------------- === Test 3: Sample 3: Long conversational rambling with false starts and slang ===Raw Input:"well i was thinking uh maybe we should... wait actually no.let's just go with the first option. because the secondoption is like way too expensive and honestly speaking wedon't have the bandwidth to build a custom api from scratchright now anyway. so yeah let's schedule a meeting tomorrowat nine am to align the team." Corrected:"Well, I was thinking maybe we should... wait, actually, no. Let's just go with the first option. Because the second option is like way too expensive, and honestly speaking, we don't have the bandwidth to build a custom API from scratch right now, anyway. So, yeah, let's schedule a meeting tomorrow at nine am to align the team." --------------------------------------------------------------------------------=== Test 1: Sample 1: Heavy disfluencies, repetitions, and grammar errors ===Raw Input:"so basically uh the the projt dedline is next mondy. rght?but like... we we haven't even got the feedback from theclient yet and i'm like super worried we gonna miss it.um, can you check with john?"Corrected:"So basically, the project deadline is next Monday. Right?But like... we haven't even got the feedback from theclient yet, and I'm like super worried we're gonna miss it.Can you check with John?"--------------------------------------------------------------------------------=== Test 2: Sample 2: Highly technical, microphone noise, lack of punctuation, and phonetic spelling ===Raw Input:"ok so the database connection string is like totally broken. bzz. we are getting connection timeout errors on port fivefour three two and i think the host name shouldbe db dot internal dot local instead of localhost rght?pls check the yaml config immediately"Corrected:"The database connection string is like totally broken. We are getting connection timeout errors on port five four three two and I think the host nameshould be `db.internal.local` instead of `localhost`, right? Please check the YAML config immediately."--------------------------------------------------------------------------------=== Test 3: Sample 3: Long conversational rambling with false starts and slang ===Raw Input:"well i was thinking uh maybe we should... wait actually no.let's just go with the first option. because the secondoption is like way too expensive and honestly speaking wedon't have the bandwidth to build a custom api from scratchright now anyway. so yeah let's schedule a meeting tomorrowat nine am to align the team."Corrected:"Well, I was thinking maybe we should... wait, actually, no. Let's just go with the first option. Because the second option is like way too expensive, and honestly speaking, we don't have the bandwidth to build a custom API from scratch right now, anyway.So, yeah, let's schedule a meeting tomorrow at nine am to align the team."--------------------------------------------------------------------------------