Views
No views yet
ahalt/qwen3-event-extraction-exp5.1,
the attribute-extraction model for NGEC
(Next Generation Event Coder). See that repo's model card for what the model does,
its evaluation numbers, and the full prompt format.convert_hf_to_gguf.py --outtype bf16 followed by llama-quantize ... Q8_0 (8.5 bits/weight). No importance matrix was used — at Q8_0 the
quantization is close enough to lossless that it isn't needed; see
llama.cpp's quantize docs.llama-server -m qwen3-event-extraction-exp5.1-Q8_0.gguf --port 8080 -c 8192llama-server's
/v1/chat/completions endpoint applies it the same way tokenizer .apply_chat_template(..., enable_thinking=False) does on the Python side. Use the
same system prompt and message format documented on the base model's card — the
## Document: … ## Event Type: <definition> v5 format, not the format the older
ahalt/event-attribute-extractor GGUFs use:1curl http://127.0.0.1:8080/v1/chat/completions \
2 -H "Content-Type: application/json" \
3 -d '{
4 "messages": [
5 {"role": "system", "content": "Given the event type definition below, find all instances of that event in the document and extract their attributes as JSON. ..."},
6 {"role": "user", "content": "## Document: ... \n\n## Event Type: ## Event: **PROTEST**: ..."}
7 ],
8 "temperature": 0.5,
9 "top_p": 0.8,
10 "top_k": 20,
11 "presence_penalty": 1.5,
12 "max_tokens": 2048
13 }'ngec.attribute_model.AttributeModel(backend="llamacpp")
builds this request for you — point llamacpp_url at a running llama-server and
model_name/NGEC_ATTRIBUTE_MODEL at ahalt/qwen3-event-extraction-exp5.1 so the
prompt format is picked correctly (the GGUF supplies weights; the Python side still
needs the tokenizer/prompt-format pairing). See demo/deploy/README.md for a
supervised deployment of llama-server on a CPU host.demo/DESIGN.md's "Two backends"
section in the NGEC repo for the comparison methodology.