qwen25-1.5b-parcel-normalizer

Qwen2.5-1.5B Parcel Record Normalizer

Fine-tuned for the Covent LLM Challenge: a small, narrow-task model that normalizes messy US property/parcel records into a fixed JSON schema.

Model Description

Real-world US county property data comes in wildly inconsistent formats, different field names, merged vs. split address components, inconsistent abbreviations, missing fields, depending on the county and platform (ArcGIS, Socrata, etc.). This model takes a messy, free-text-style property record and outputs clean, structured JSON in one fixed canonical schema:

{
  "parcel_id": "",
  "situs_address": "",
  "situs_city": "",
  "situs_state": "",
  "situs_zip": "",
  "owner_name": "",
  "owner_mailing_address": "",
  "owner_mailing_city": "",
  "owner_mailing_state": "",
  "owner_mailing_zip": ""
}

• Developed by: Afshan
• Model type: LoRA adapter (r=16) on Qwen2.5-1.5B-Instruct, 4-bit quantized
• Language: English
• License: Apache 2.0 (inherited from base model)
• Finetuned from: unsloth/Qwen2.5-1.5B-Instruct-bnb-4bit

Training Data

~2,850 real-world-derived training pairs built from live public parcel records:

• Cook County, IL (Socrata Open Data API)
• DuPage County, IL (ArcGIS REST API)

Each pair consists of a real record synthetically corrupted (abbreviation swaps, typos, punctuation dropping, casing variation, multiple free-text templates) paired with the correct clean JSON as the training target.

Evaluation

Evaluated on 300 real records from three counties never seen during training, Maricopa County (AZ), Travis County (TX), and Denver County (CO), against Claude Opus 4.8 as the frontier baseline, using an identical system prompt for both models.

Opus 4.8 outperforms on fields requiring broad US geographic world-knowledge (city/state/zip associations it learned from pretraining). This model wins specifically on owner mailing address fields, a narrower, structural pattern (owner mailing address often matches situs address when not explicitly stated) learned from real training data rather than world knowledge. parcel_id is excluded from scoring since it never appears in the input text and is unknowable by construction for either model.

Full eval script and raw predictions: see the GitHub repo https://github.com/Afshan738/covent-llm-challenge.

How to Use

from unsloth import FastLanguageModel

model, tokenizer = FastLanguageModel.from_pretrained(
    model_name="Afshanqasim525/qwen25-1.5b-parcel-normalizer",
    max_seq_length=512,
    load_in_4bit=True,
)
FastLanguageModel.for_inference(model)

SYSTEM_PROMPT = (
    "You normalize messy US property records into a fixed JSON schema. "
    "Given a raw record, output ONLY valid JSON with exactly these keys: "
    "parcel_id, situs_address, situs_city, situs_state, situs_zip, "
    "owner_name, owner_mailing_address, owner_mailing_city, "
    "owner_mailing_state, owner_mailing_zip. "
    "If a value is unknown, use null. Do not add commentary."
)

messages = [
    {"role": "system", "content": SYSTEM_PROMPT},
    {"role": "user", "content": "Normalize this record:\n75 LEO CT roselle IL 60172\nOwner: STOESSER, JAMES L"},
]
inputs = tokenizer.apply_chat_template(messages, tokenize=True, add_generation_prompt=True, return_tensors="pt")
out = model.generate(inputs, max_new_tokens=200, temperature=0.1, do_sample=False)
print(tokenizer.decode(out[0][inputs.shape[1]:], skip_special_tokens=True))

Training Hyperparameters

• Base model: Qwen2.5-1.5B-Instruct (4-bit QLoRA)
• LoRA: r=16, alpha=16, targeting q/k/v/o and gate/up/down projections
• Epochs: 2, learning rate: 2e-4, batch size: 8 (x2 grad accumulation)
• Hardware: single T4 GPU (free-tier Colab)

Limitations

• Training data comes from only two Illinois counties; performance on other states' formatting conventions is evaluated but not deeply optimized.
• Frontier baseline comparisons were originally planned against Gemini 3.1 Pro as a lower-cost option, but a regional free-tier access restriction (unrelated to usage/quota) made this infeasible; Claude Opus 4.8 was used instead via the standard API.
• This is a proof-of-concept demonstrating narrow-task specialization, not a production-ready system.

Framework versions

• PEFT 0.19.1