Is it good enough?
This page is a projection of the one entry record, the Reliability factor that Use covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.
- AssessUse & modify + Transparency
- ImplementData control + Reliability
- UseReliability
- SupportTransparency
Capabilities & modalities
Text reasoning models (maths, coding, analysis) distilled from R1 into dense 1.5B-32B weights. They emit explicit reasoning traces (think tags). They are strong for their size, most of all the 14B and 32B.
Context window & long-context behaviour
The cards declare a 128K-token context, from the Qwen2.5 bases. OneHill has not measured effective long-context recall, so treat 128K as the declared window.
Prompt format & chat template
The models ship a chat template with the R1 reasoning (think-tag) convention. Use
apply_chat_template and decide in the client whether to expose or strip the reasoning segment.
Language coverage
English and Chinese are strongest (Qwen2.5 base plus R1 distillation). Depth in other languages varies with model size.
Function / tool calling
These are reasoning distils. Native tool calling is not their primary documented behaviour and is unverified. Confirm per serving stack and size, and test.
Structured / JSON-constrained output
No native JSON or schema-constrained output guarantee is documented. Constrained decoding is a serving-layer feature, available through vLLM and SGLang grammars.
How this scores
The ownership factor this domain covers, drawn from the one entry record.
ReliabilityIs it reliable and good enough for the job?
StrongPerformance 3, operational 5 and safety 3: solid reasoning for the size and the easiest serving in the family. All three are at or above 3 and operational is 5, so reliability is strong. The gap is the absence of safety tuning and of a first-party guard model.
Sources
The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.