Skip to content
AI NEWS JOURNAL
AI, IN PERSPECTIVE

Search AI news

Search headlines, summaries and articles to connect the dots.

Newest first

ProcessPrefBench: Evaluating Cross-Task Transfer of Individual Process Preferences from Naturalistic Human-AI Interaction

arXiv:2611.06065v1 Announce Type: new Abstract: In natural human-AI dialogue, users' corrections, requests, and self-descriptions carry reusable signals about how they want work to be done. These signals reveal individual process preferences, user-specific standards for evidence, depth, analytical focus, procedure, and delivery. We ask whether a preference revealed in one dialogue can shape an assistant's later answer when the task does not restate it. ProcessPrefBench uses three months of natural dialogues from two knowledge workers to build 66 source-target cases separately judged for source evidence and target applicability. Sources are preselected, so the benchmark tests application rather than retrieval. We test three models with target-only, full-history, and distilled-preference prompts. Target-specific 0-2 rubrics score preference realization, and a task gate flags severe failures. Compared with target-only prompting, full-history and imperative distilled-preference prompting raise preference realization by 0.204 and 0.244 points on the 0-2 scale, respectively, with no reliable advantage from distillation. Fabricated-evidence failures rise from 5.8% under target-only prompting to 10.1% under full-history and 10.4% under imperative prompting. ProcessPrefBench highlights a tension in learning from dialogue, where drawing on prior interactions can improve preference realization yet also invite fabricated evidence. We hope it helps build assistants that honor a user's process preferences without sacrificing factual reliability.

Show HN: Alternative to Nvidia Auto-Ontology

This repo provides an alternative to the ontology compiling capabilities of NVIDA Auto-Ontology.The main difference is that it builds the ontology from most of your existing data assets (transformation code, dashboards, docs), instead of building it from your warehouse and semantic layer only.It consists in skills and python scripts that ingest the metadata and docs your team already has, and compile them into YAML and Markdown files structured in a file tree that an agent can use as context to query your data.When your existing asset contradict, or reveal a gap in the business context around your data, it writes down questions for you and your team instead of guessing a plausible meaning.It runs locally in any coding agent. Comments URL: https://news.ycombinator.com/item?id=50363667 Points: 1 # Comments: 0