Gemma 4 E4B IT vs OTel-2.0-LLM-31B-IT

Gemma 4 E4B IT 95

Memory 30, Google's own 4-bit QAT GGUF with its projector is 6.15 GB, which with a fifth on top is 7.4 GB and fits in 16 GB or less. Runtimes 25, released support in Transformers, vLLM, SGLang, llama.cpp, Ollama and LM Studio, six of six. Builds 15, Google publishes a Q4_0 GGUF and a w4a16 build and two mobile builds, read as two kinds as for the 31B. Terms 15, plain Apache 2.0 with nothing added. Download 10, no account or gate. Hosted 0, the Gemini API serves only the two largest sizes and no inference provider lists this one.

OTel-2.0-LLM-31B-IT 50

Memory 10, the publisher's only build is the BF16 safetensors, 62.55 GB for the 15 shards the index names, and 62.55 GB × 1.2 = 75.1 GB, above 64 GB and inside the reference machine's GPU share. Runtimes 15, the architecture is Gemma4ForConditionalGeneration, which vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 run from the safetensors files, three at 5 each. Builds 0, the publisher ships the BF16 weights only. Terms 15, Apache 2.0 in the card's metadata, an OSI licence, with nothing added on the card. Download 10, gated is false on 10 November 2026, so the files download with no account or terms. Hosted 0, Hugging Face maps one inference provider, Featherless AI (live), short of the two the line needs. 10 + 15 + 0 + 15 + 10 + 0 = 50.

Gemma 4 E4B IT 85

Chat template 20, a Jinja file in the repository. Tool-calling format 25, Google documents how tools are declared and how calls come back, and ships a response schema for Transformers' parser. Trained tool calling 20, several calls in one turn. Structured output 0, nothing documents how to ask the weights for JSON or a schema. Reasoning control 10, thinking is off by default, turned on per request, and returned in a thought channel. Context 10, 131,072 tokens native, which meets the 128K line.

OTel-2.0-LLM-31B-IT 60

Chat template 20, chat_template.jinja in the repository, 19,300 characters, the publisher's own. Tool-calling format 10, only the template says how tools are declared and how calls come back. Trained tool calling 20, the template loops over tool_calls, so it renders several calls in one turn, and the card says the training mix included general-purpose agentic tool-calling examples, while none were specific to telecoms. Structured output 0, the card doesn't document JSON or JSON Schema output. Reasoning control 0, the card says the model wasn't trained to produce or consume Gemma's thought channel and answers directly, so there is no thinking to switch or budget. Context 10, 262,144 positions in the text config, the base's native context. 20 + 10 + 20 + 0 + 0 + 10 = 60.

Gemma 4 E4B IT 70

File safety 25, safetensors and GGUF only, with nothing from the repository run on load. Provenance 15, the files sit in Google's own organisation and every file has a checksum. Safety evaluation 0, the card says testing showed minimal policy violations but gives no figures. Agent guidance 10, the card names the harm categories its safety training covers and asks for content-safety safeguards, and the tool guide says to validate calls, with no prompt-injection guidance. Licence risk 15, Apache 2.0 with no added policy, no threshold and a working link. Security programme 5, Google's security.txt and reward programme give a route to report a flaw, but no public Gemma advisories were found.

OTel-2.0-LLM-31B-IT 55

File safety 25, safetensors only, with no .bin, .pt or .pth files and no Python files. Provenance 5, the files sit in a personal account, farbodtavakkoli, not in an organisation AT&T's or GSMA's site links to: GSMA's article names AT&T as the releaser without linking the repository, and the GitHub repository that links it is the same person's (0). Safety evaluation 0, no safety results on the card. Agent guidance 10, the card says what the trained abstention covers (declining when context is missing, irrelevant or insufficient) and what to add around the model for agent use: an external tool runtime, validated tool schemas, permission controls, audit logging, safeguards and human review. Licence risk 15, Apache 2.0 has no use policy, field-of-use limit, threshold or change clause, nothing is added on the card, and the licence link resolves (200 on 10 November 2026). Security programme 0, no way to report a flaw found. 25 + 5 + 0 + 10 + 15 + 0 = 55.