[{"data":1,"prerenderedAt":413},["ShallowReactive",2],{"insight-llm-domain-ontology":3,"insight-related-llm-domain-ontology":149},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":7,"slug":9,"date":10,"duration":11,"category":12,"author":13,"tags":14,"body":19,"_type":143,"_id":144,"_source":145,"_file":146,"_stem":147,"_extension":148},"\u002Finsights\u002F05-llm-domain-ontology","insights",false,"","让 LLM 读懂业务术语：从 Prompt 工程到企业本体","llm-domain-ontology","2026-02-15",9,"AI 工程","浩途技术团队",[15,16,17,18],"LLM","Prompt","企业本体","ontology",{"type":20,"children":21,"toc":136},"root",[22,30,44,48,53,88,93,96,102,107,116,119,124],{"type":23,"tag":24,"props":25,"children":27},"element","h2",{"id":26},"引子",[28],{"type":29,"value":26},"text",{"type":23,"tag":31,"props":32,"children":33},"p",{},[34,36,42],{"type":29,"value":35},"为某银行做信贷智能助手时，反复调试 Prompt 让 LLM 理解\"客户经理\"和\"产品经理\"\n的区别——失败。意识到：",{"type":23,"tag":37,"props":38,"children":39},"strong",{},[40],{"type":29,"value":41},"业务术语的歧义不是 Prompt 能解决的",{"type":29,"value":43},"，需要从源头注入\n企业本体（ontology）。",{"type":23,"tag":45,"props":46,"children":47},"hr",{},[],{"type":23,"tag":24,"props":49,"children":51},{"id":50},"业务术语的三种歧义",[52],{"type":29,"value":50},{"type":23,"tag":54,"props":55,"children":56},"ol",{},[57,68,78],{"type":23,"tag":58,"props":59,"children":60},"li",{},[61,66],{"type":23,"tag":37,"props":62,"children":63},{},[64],{"type":29,"value":65},"同名异义",{"type":29,"value":67},"：客户经理（银行）vs 客户经理（地产）",{"type":23,"tag":58,"props":69,"children":70},{},[71,76],{"type":23,"tag":37,"props":72,"children":73},{},[74],{"type":29,"value":75},"异名同义",{"type":29,"value":77},"：业务员 \u002F 客户经理 \u002F 销售代表 在同一企业并存",{"type":23,"tag":58,"props":79,"children":80},{},[81,86],{"type":23,"tag":37,"props":82,"children":83},{},[84],{"type":29,"value":85},"关系隐含",{"type":29,"value":87},"：A 部门的\"主管\"对 B 部门的人是否有审批权？",{"type":23,"tag":31,"props":89,"children":90},{},[91],{"type":29,"value":92},"LLM 默认按通用语料解读，95% 场景能蒙对，关键 5% 决策上会翻车。",{"type":23,"tag":45,"props":94,"children":95},{},[],{"type":23,"tag":24,"props":97,"children":99},{"id":98},"解法业务本体显式建模-检索增强",[100],{"type":29,"value":101},"解法：业务本体显式建模 + 检索增强",{"type":23,"tag":31,"props":103,"children":104},{},[105],{"type":29,"value":106},"把企业的角色 \u002F 实体 \u002F 关系 \u002F 流程做成结构化本体，作为系统级 Prompt 的固定上下文，\n或在 RAG 时优先召回相关本体片段。",{"type":23,"tag":108,"props":109,"children":110},"blockquote",{},[111],{"type":23,"tag":31,"props":112,"children":113},{},[114],{"type":29,"value":115},"（具体本体格式、注入策略、性能取舍待后续）",{"type":23,"tag":45,"props":117,"children":118},{},[],{"type":23,"tag":24,"props":120,"children":122},{"id":121},"写在最后",[123],{"type":29,"value":121},{"type":23,"tag":31,"props":125,"children":126},{},[127,129,134],{"type":29,"value":128},"Prompt 是表达力工具，本体是知识基础设施。",{"type":23,"tag":37,"props":130,"children":131},{},[132],{"type":29,"value":133},"两件事不能互相替代",{"type":29,"value":135},"——这是把 LLM 接进\n企业的核心方法论。",{"title":7,"searchDepth":137,"depth":137,"links":138},2,[139,140,141,142],{"id":26,"depth":137,"text":26},{"id":50,"depth":137,"text":50},{"id":98,"depth":137,"text":101},{"id":121,"depth":137,"text":121},"markdown","content:insights:05-llm-domain-ontology.md","content","insights\u002F05-llm-domain-ontology.md","insights\u002F05-llm-domain-ontology","md",[150,293],{"_path":151,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":152,"description":7,"slug":153,"date":154,"duration":155,"category":12,"author":13,"cover":156,"tags":157,"featured":161,"body":162,"_type":143,"_id":290,"_source":145,"_file":291,"_stem":292,"_extension":148},"\u002Finsights\u002F01-agent-pitfalls","把 Agent 接进真实业务系统时，我们踩过的 7 个坑","agent-7-pitfalls","2026-04-18",14,"\u002Fimages\u002Finsights\u002Fagent-pitfalls-cover.png",[158,15,159,160],"Agent","RAG","业务系统",true,{"type":20,"children":163,"toc":283},[164,168,173,176,182,190,195,212,215,221,226,229,235,264,267,271],{"type":23,"tag":24,"props":165,"children":166},{"id":26},[167],{"type":29,"value":26},{"type":23,"tag":31,"props":169,"children":170},{},[171],{"type":29,"value":172},"2024 年起，浩途陆续把 LLM Agent 嵌入到客户的真实业务系统里——审批流、知识问答、\n工单分发、报表分析等。一年下来，复盘了 7 类反复踩过的坑，写下来给同行做避雷参考。",{"type":23,"tag":45,"props":174,"children":175},{},[],{"type":23,"tag":24,"props":177,"children":179},{"id":178},"坑-1权限边界没想清楚就让-agent-全能",[180],{"type":29,"value":181},"坑 1：权限边界没想清楚就让 Agent \"全能\"",{"type":23,"tag":108,"props":183,"children":184},{},[185],{"type":23,"tag":31,"props":186,"children":187},{},[188],{"type":29,"value":189},"现象：Agent 调用 API 时，能看到不属于本用户的数据。",{"type":23,"tag":31,"props":191,"children":192},{},[193],{"type":29,"value":194},"业务系统的权限模型通常是基于\"会话用户\"的，但 Agent 工作时是另一个身份。\n我们最早的做法是给 Agent 一个\"超级账号\"——很快就出问题：审批流里，Agent 帮 A 用户\n看了 B 用户的工单详情。",{"type":23,"tag":31,"props":196,"children":197},{},[198,203,205,210],{"type":23,"tag":37,"props":199,"children":200},{},[201],{"type":29,"value":202},"Plan B",{"type":29,"value":204},"：让 Agent ",{"type":23,"tag":37,"props":206,"children":207},{},[208],{"type":29,"value":209},"以调用者身份",{"type":29,"value":211},"访问业务 API，所有权限控制由原系统继承。",{"type":23,"tag":45,"props":213,"children":214},{},[],{"type":23,"tag":24,"props":216,"children":218},{"id":217},"坑-2上下文窗口一旦满了行为就开始抖",[219],{"type":29,"value":220},"坑 2：上下文窗口一旦满了，行为就开始抖",{"type":23,"tag":31,"props":222,"children":223},{},[224],{"type":29,"value":225},"（… 因篇幅省略，正文未来由内容运营补齐 …）",{"type":23,"tag":45,"props":227,"children":228},{},[],{"type":23,"tag":24,"props":230,"children":232},{"id":231},"坑-37占位",[233],{"type":29,"value":234},"坑 3—7：（占位）",{"type":23,"tag":236,"props":237,"children":238},"ul",{},[239,244,249,254,259],{"type":23,"tag":58,"props":240,"children":241},{},[242],{"type":29,"value":243},"幻觉与业务规则的协调",{"type":23,"tag":58,"props":245,"children":246},{},[247],{"type":29,"value":248},"工具调用的失败重试",{"type":23,"tag":58,"props":250,"children":251},{},[252],{"type":29,"value":253},"多轮对话状态管理",{"type":23,"tag":58,"props":255,"children":256},{},[257],{"type":29,"value":258},"成本失控与模型路由",{"type":23,"tag":58,"props":260,"children":261},{},[262],{"type":29,"value":263},"灰度上线与可回滚",{"type":23,"tag":45,"props":265,"children":266},{},[],{"type":23,"tag":24,"props":268,"children":269},{"id":121},[270],{"type":29,"value":121},{"type":23,"tag":31,"props":272,"children":273},{},[274,276,281],{"type":29,"value":275},"把 LLM 接进业务系统，难的不是模型，而是 ",{"type":23,"tag":37,"props":277,"children":278},{},[279],{"type":29,"value":280},"业务约束如何被表达成 Agent 能理解的规则",{"type":29,"value":282},"。\n浩途下一篇会写\"如何把审批流的 50 条规则，结构化喂给 Agent 而不超 token\"。",{"title":7,"searchDepth":137,"depth":137,"links":284},[285,286,287,288,289],{"id":26,"depth":137,"text":26},{"id":178,"depth":137,"text":181},{"id":217,"depth":137,"text":220},{"id":231,"depth":137,"text":234},{"id":121,"depth":137,"text":121},"content:insights:01-agent-pitfalls.md","insights\u002F01-agent-pitfalls.md","insights\u002F01-agent-pitfalls",{"_path":294,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":295,"description":7,"slug":296,"date":297,"duration":298,"category":12,"author":13,"tags":299,"body":301,"_type":143,"_id":410,"_source":145,"_file":411,"_stem":412,"_extension":148},"\u002Finsights\u002F04-rag-knowledge-gap","RAG 在企业内的\"知识断层\"——为什么准确率上不去","rag-knowledge-gap","2026-03-22",11,[159,300,15],"企业知识库",{"type":20,"children":302,"toc":404},[303,307,319,322,328,340,350,353,359,377,385,388,392],{"type":23,"tag":24,"props":304,"children":305},{"id":26},[306],{"type":29,"value":26},{"type":23,"tag":31,"props":308,"children":309},{},[310,312,317],{"type":29,"value":311},"把 PDF 制度、Wiki、邮件归档全部 embedding 进 RAG 系统后，业务部门用了一周回来反馈：\n\"答案看起来对，细节都不对\"。我们复盘了 4 个项目的 RAG 准确率数据，得出的结论是\n——问题不在 embedding 模型，而在",{"type":23,"tag":37,"props":313,"children":314},{},[315],{"type":29,"value":316},"企业知识本身的断层",{"type":29,"value":318},"。",{"type":23,"tag":45,"props":320,"children":321},{},[],{"type":23,"tag":24,"props":323,"children":325},{"id":324},"断层-1切片粒度不匹配业务粒度",[326],{"type":29,"value":327},"断层 1：切片粒度不匹配业务粒度",{"type":23,"tag":31,"props":329,"children":330},{},[331,333,338],{"type":29,"value":332},"文档切片用 token 长度分块，业务问题却以\"任务\"为单位。一个\"如何提报年终预算\"\n跨 3 份文档：制度、流程图、表格模板。RAG 召回的 3 个 chunk 来自 3 份文档，但\n",{"type":23,"tag":37,"props":334,"children":335},{},[336],{"type":29,"value":337},"chunk 之间没有上下文链接",{"type":29,"value":339},"——LLM 无法重组成完整答案。",{"type":23,"tag":31,"props":341,"children":342},{},[343,348],{"type":23,"tag":37,"props":344,"children":345},{},[346],{"type":29,"value":347},"做法",{"type":29,"value":349},"：按业务任务建知识图谱，chunk 之上加\"任务-文档\"映射。",{"type":23,"tag":45,"props":351,"children":352},{},[],{"type":23,"tag":24,"props":354,"children":356},{"id":355},"断层-234占位",[357],{"type":29,"value":358},"断层 2、3、4（占位）",{"type":23,"tag":236,"props":360,"children":361},{},[362,367,372],{"type":23,"tag":58,"props":363,"children":364},{},[365],{"type":29,"value":366},"部门术语演化：同一个词在 IT 和业务部分别意指不同",{"type":23,"tag":58,"props":368,"children":369},{},[370],{"type":29,"value":371},"时间维度断层：旧规章和新规章并存，RAG 不知道哪个生效",{"type":23,"tag":58,"props":373,"children":374},{},[375],{"type":29,"value":376},"隐性知识缺失：流程之外的\"惯例\"从来没写进文档",{"type":23,"tag":108,"props":378,"children":379},{},[380],{"type":23,"tag":31,"props":381,"children":382},{},[383],{"type":29,"value":384},"（详细案例与方法论由后续内容运营展开）",{"type":23,"tag":45,"props":386,"children":387},{},[],{"type":23,"tag":24,"props":389,"children":390},{"id":121},[391],{"type":29,"value":121},{"type":23,"tag":31,"props":393,"children":394},{},[395,397,402],{"type":29,"value":396},"RAG 不是把文档塞进向量库就行。",{"type":23,"tag":37,"props":398,"children":399},{},[400],{"type":29,"value":401},"先治理知识，再做 RAG",{"type":29,"value":403},"——这才是企业落地 LLM 的正确顺序。",{"title":7,"searchDepth":137,"depth":137,"links":405},[406,407,408,409],{"id":26,"depth":137,"text":26},{"id":324,"depth":137,"text":327},{"id":355,"depth":137,"text":358},{"id":121,"depth":137,"text":121},"content:insights:04-rag-knowledge-gap.md","insights\u002F04-rag-knowledge-gap.md","insights\u002F04-rag-knowledge-gap",1780542368482]