LocalIntent: Outcome-Specific Structured Generation for Backend-Compatible Smart Building Automation with Local LLMs
Organizations: Beijing Dublin International College, University College Dublin, Beijing, China · School of Computer Science, University College Dublin, Dublin, Ireland
Abstract
Locally deployed large language models (LLMs) can reduce reliance on remote cloud services for natural language smart building automation, but backend-facing processing requires correct outcome selection, alignment with local capabilities, and valid structured outputs. We investigate whether a complete outcome-specific prompting design improves compact-model outputs beyond generic route-then-generate prompting. The proposed LocalIntent approach routes requests to ordinary or persistent-rule branches: the former produces commands, clarifications, or rejections, while the latter generates trigger-action rules, followed by deterministic validation. We evaluate four locally executed Gemma and Qwen models spanning 2B-9B parameters on 101 non-persistent and 54 persistent-rule records, comparing Monolithic prompting, generic two-stage prompting, LocalIntent, and validation-guided repair. Across the evaluated datasets, LocalIntent achieves higher intent understanding, device identification, and action/parameter correctness than generic two-stage prompting, while clarification/mode correctness remains model-dependent. The largest gains occur for rules, where LocalIntent improves intent understanding from 26.4% to 80.6%, device identification from 59.3% to 84.7%, rule-mode correctness from 49.1% to 98.6%, and action/parameter correctness from 5.6% to 44.9%. For non-persistent requests, pooled gains are smaller: intent understanding increases from 39.6% to 53.2%, and action/parameter correctness from 30.7% to 42.8%.
Figures & tables
| Outcome | Semantic fields | Generation guidance |
|---|---|---|
| Command | target, action, parameters | Preserve immediate semantics. Select a registered target and supported action. Provide the required valid parameters. Do not introduce rule fields or infer unresolved information. |
| Rule | predicate-bearing trigger, action | Preserve persistent semantics. Map the trigger to a registered sensor and supported predicate. Select a supported action. Maintain consistency between the trigger predicate and action. Do not represent the action as immediate execution. |
| Clarification | unresolved element, question | Identify the information preventing an otherwise supported completion. Request only the information needed to continue. Do not generate command or rule fields. |
| Rejection | unsupported element, reason | Identify the requested functionality that is unavailable under the registered capabilities or platform scope. Do not generate command or rule fields. |
LLM Prompting
Large language model prompting studies how instructions, examples, context, and formats steer model behavior at inference time.
See all 429 papers