Granite Speech 5.0 TurboCTC vs Ternary Bonsai 27B
At a Glance
| Compare | Ternary Bonsai 27BPrismML | |
|---|---|---|
| Pricing and Limits | ||
| Context windowMaximum documented tokens | Not reported | 262K |
| Model facts checked | Sep 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
Side-by-Side Facts
| Field | Granite Speech 5.0 TurboCTC | Ternary Bonsai 27B |
|---|---|---|
| Developer | IBM | PrismML |
| Family | Granite Speech 5 0 | Bonsai 27b |
| Model | Granite Speech 5.0 TurboCTC | Ternary Bonsai 27B |
| Version | Granite Speech 5.0 TurboCTC | Ternary Bonsai 27B |
| Lifecycle | active | active |
| Released | 2026-08-25 | 2026-07-04 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Audio | Text, Image |
| Output modalities | Text | Text |
| Context window | Unknown | 262K |
| Total parameters | 473M | 27B |
| Active parameters | Unknown | Unknown |
| License | apache-2.0 | apache-2.0 |
| Open weights | Yes | Yes |
| API available | No | Yes |
| Self-hostable | Yes | Yes |
| Provider access | Unknown | Together Ai (Standard) |
| Capabilities | automatic-speech-recognition, transcription | chat, generation, reasoning, tools, vision |
| Base model | Unknown | Qwen3.6 27B |
| Effective bit width | Unknown | 1.58 bits per weight |
| Language model size | Unknown | 6.66 GiB |
| Weight format | Unknown | Ternary Q2_0 |
Granite Speech 5.0 TurboCTC Capabilities
Ternary Bonsai 27B Capabilities
Primary Evidence
Sources and Freshness
Questions
Granite Speech 5.0 TurboCTC vs Ternary Bonsai 27B FAQs
Is Granite Speech 5.0 TurboCTC or Ternary Bonsai 27B better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Granite Speech 5.0 TurboCTC and Ternary Bonsai 27B, 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 27B?+
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 27B?+
Neither model has a larger sourced context window in this comparison. Granite Speech 5.0 TurboCTC is — and Ternary Bonsai 27B is 262K.
Which performs better in benchmarks, Granite Speech 5.0 TurboCTC or Ternary Bonsai 27B?+
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 27B be self-hosted?+
Both models have the same recorded self-hosting status: supported. Granite Speech 5.0 TurboCTC is open weight; Ternary Bonsai 27B is open weight.
Can Granite Speech 5.0 TurboCTC and Ternary Bonsai 27B understand images?+
Granite Speech 5.0 TurboCTC is not documented with image input; Ternary Bonsai 27B is 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 27B?+
Neither has a larger sourced maximum output. Granite Speech 5.0 TurboCTC is — and Ternary Bonsai 27B is —.
Do Granite Speech 5.0 TurboCTC and Ternary Bonsai 27B support reasoning and tool use?+
Granite Speech 5.0 TurboCTC: none of these features are definitively sourced. Ternary Bonsai 27B: reasoning, tool calling, and image input. Feature support does not establish relative quality.
Which is available from more inference providers, Granite Speech 5.0 TurboCTC or Ternary Bonsai 27B?+
Granite Speech 5.0 TurboCTC has 0 sourced provider routes; Ternary Bonsai 27B has 1, so Ternary Bonsai 27B has broader tracked availability.
Which offers better value, Granite Speech 5.0 TurboCTC or Ternary Bonsai 27B?+
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.