Granite Speech 5.0 TurboCTC vs Ternary Bonsai 4B

At a Glance

Compare
Pricing and Limits
Context windowMaximum documented tokensNot reported33K
Model facts checkedSep 2, 2026View model evidence →Sep 18, 2026View model evidence →

Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →

Available Benchmarks

All benchmark results →
No Protocol-Matched Benchmark Yet.Results appear here only when both models share the same benchmark version, metric, evaluation protocol, and evidence class.

Side-by-Side Facts

FieldGranite Speech 5.0 TurboCTCTernary Bonsai 4B
DeveloperIBMPrismML
FamilyGranite Speech 5 0Bonsai 4b
ModelGranite Speech 5.0 TurboCTCTernary Bonsai 4B
VersionGranite Speech 5.0 TurboCTCTernary Bonsai 4B
Lifecycleactiveactive
Released2026-08-252026-04-18
Knowledge cutoffUnknownUnknown
Input modalitiesAudioText
Output modalitiesTextText
Context windowUnknown33K
Total parameters473M4B
Active parametersUnknownUnknown
Licenseapache-2.0apache-2.0
Open weightsYesYes
API availableNoNo
Self-hostableYesYes
Provider accessUnknownUnknown
Capabilitiesautomatic-speech-recognition, transcriptionchat, generation
Effective bit widthUnknown1.58 bits per weight
Weight sizeUnknown1.07 GB
Weight formatUnknownTernary Q2_0

Granite Speech 5.0 TurboCTC Capabilities

automatic-speech-recognitiontranscription
Serving providers0
Canonical IDibm-granite/granite-speech-5.0-470m-turboctc

Ternary Bonsai 4B Capabilities

chatgeneration
Serving providers0
Canonical IDprism-ml/Ternary-Bonsai-4B

Primary Evidence

Sources and Freshness

Questions

Granite Speech 5.0 TurboCTC vs Ternary Bonsai 4B FAQs

Is Granite Speech 5.0 TurboCTC or Ternary Bonsai 4B better for coding?+

This comparison does not currently contain a protocol-matched coding benchmark for both Granite Speech 5.0 TurboCTC and Ternary Bonsai 4B, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.

Which is cheaper, Granite Speech 5.0 TurboCTC or Ternary Bonsai 4B?+

Neither model has a directly sourced input price in this comparison. Neither model has a directly sourced output price in this comparison.

Which has a larger context window, Granite Speech 5.0 TurboCTC or Ternary Bonsai 4B?+

Neither model has a larger sourced context window in this comparison. Granite Speech 5.0 TurboCTC is — and Ternary Bonsai 4B is 33K.

Which performs better in benchmarks, Granite Speech 5.0 TurboCTC or Ternary Bonsai 4B?+

There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.

Can Granite Speech 5.0 TurboCTC or Ternary Bonsai 4B be self-hosted?+

Both models have the same recorded self-hosting status: supported. Granite Speech 5.0 TurboCTC is open weight; Ternary Bonsai 4B is open weight.

Can Granite Speech 5.0 TurboCTC and Ternary Bonsai 4B understand images?+

Granite Speech 5.0 TurboCTC is not documented with image input; Ternary Bonsai 4B is not documented with image input. This reflects supported input modalities, not vision quality.

Which can generate longer answers, Granite Speech 5.0 TurboCTC or Ternary Bonsai 4B?+

Neither has a larger sourced maximum output. Granite Speech 5.0 TurboCTC is — and Ternary Bonsai 4B is —.

Do Granite Speech 5.0 TurboCTC and Ternary Bonsai 4B support reasoning and tool use?+

Granite Speech 5.0 TurboCTC: none of these features are definitively sourced. Ternary Bonsai 4B: none of these features are definitively sourced. Feature support does not establish relative quality.

Which is available from more inference providers, Granite Speech 5.0 TurboCTC or Ternary Bonsai 4B?+

Granite Speech 5.0 TurboCTC has 0 sourced provider routes; Ternary Bonsai 4B has 0, a tie.

Which offers better value, Granite Speech 5.0 TurboCTC or Ternary Bonsai 4B?+

There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.

Send Feedback