AI Hallucination Mitigation - AiPro Institute\u2122<\/title>\n <style>\n *{margin:0;padding:0;box-sizing:border-box}\n body{font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Roboto,'Helvetica Neue',Arial,sans-serif;line-height:1.6;color:#333;background:#fff;padding:2rem 1rem}\n .container{max-width:900px;margin:0 auto}\n .page-title{text-align:center;font-size:2.5rem;font-weight:700;background:linear-gradient(135deg,#667eea 0%,#764ba2 100%);-webkit-background-clip:text;-webkit-text-fill-color:transparent;background-clip:text;margin-bottom:2rem}\n .card{background:#fff;border-radius:12px;box-shadow:0 4px 6px rgba(0,0,0,.1);overflow:hidden;margin-bottom:2rem}\n .card-header{background:linear-gradient(135deg,#667eea 0%,#764ba2 100%);color:#fff;padding:2rem}\n .card-header h1{font-size:2rem;margin-bottom:.5rem}\n .card-header .subtitle{font-size:1.1rem;opacity:.95}\n .meta-badges,.tool-badges{display:flex;gap:.75rem;margin-top:1rem;flex-wrap:wrap}\n .badge{background:rgba(255,255,255,.2);padding:.4rem .9rem;border-radius:20px;font-size:.9rem;backdrop-filter:blur(10px)}\n .tool-badge{background:transparent;border:1px solid rgba(255,255,255,.4);padding:.4rem .9rem;border-radius:20px;font-size:.85rem}\n .card-body{padding:2.5rem}\n .section-title-container{display:flex;justify-content:space-between;align-items:center;margin:2.5rem 0 1.25rem 0}\n .section-title-container:first-child{margin-top:0}\n .section-title{font-size:1.75rem;color:#764ba2;border-left:4px solid #764ba2;padding-left:1rem;margin:0}\n .copy-button{background:linear-gradient(135deg,#667eea 0%,#764ba2 100%);color:#fff;border:none;padding:.6rem 1.5rem;border-radius:6px;cursor:pointer;font-size:.95rem;font-weight:500;transition:opacity .3s}\n .copy-button:hover{opacity:.9}\n .prompt-box{background:#f8f9fa;border:1px solid #dee2e6;border-radius:8px;padding:1.5rem;margin:1.25rem 0;font-family:'Courier New',monospace;font-size:.95rem;line-height:1.6;white-space:pre-wrap;overflow-x:auto}\n .placeholder{color:#fd7e14;font-weight:bold}\n .tip-box{background:#fff9e6;border-left:4px solid #ffc107;padding:1.25rem;margin:1.25rem 0;border-radius:4px}\n .tip-box strong{color:#f57c00}\n h3{color:#764ba2;font-size:1.35rem;margin:2rem 0 1rem 0}\n p{margin-bottom:1rem;line-height:1.8}\n ul,ol{margin-left:2rem;margin-bottom:1rem}\n li{margin-bottom:.5rem;line-height:1.8}\n .example-output{background:#f0f8ff;border:2px solid #4a90e2;border-radius:8px;padding:1.5rem;margin:1.25rem 0}\n .example-output h4{color:#4a90e2;margin-bottom:1rem}\n .chain-step{background:#f8f9fa;border-left:4px solid #667eea;padding:1.5rem;margin:1.5rem 0;border-radius:4px}\n .chain-step h4{color:#667eea;margin-bottom:.75rem}\n .footer{background:#f8f9fa;padding:2rem;margin-top:2rem;border-radius:8px;display:flex;justify-content:space-around;align-items:center;flex-wrap:wrap;gap:1.5rem}\n .footer-stat{text-align:center}\n .footer-stat-value{font-size:1.75rem;font-weight:700;color:#764ba2}\n .footer-stat-label{color:#666;font-size:.95rem}\n @media (max-width:768px){.page-title{font-size:1.75rem}.card-header h1{font-size:1.5rem}.card-body{padding:1.5rem}.section-title{font-size:1.35rem}.section-title-container{flex-direction:column;align-items:flex-start;gap:1rem}.footer{flex-direction:column}}\n <\/style>\n<\/head>\n<body>\n <div class=\"container\">\n <h1 class=\"page-title\">AI Hallucination Mitigation<\/h1>\n\n <div class=\"card\">\n <div class=\"card-header\">\n <h1>AI Hallucination Mitigation<\/h1>\n <p class=\"subtitle\">AI Safety & Governance<\/p>\n <div class=\"meta-badges\">\n <span class=\"badge\">\u23f1\ufe0f 30-45 minutes<\/span>\n <span class=\"badge\">\ud83d\udcca Advanced<\/span>\n <\/div>\n <div class=\"tool-badges\">\n <span class=\"tool-badge\">ChatGPT<\/span>\n <span class=\"tool-badge\">Claude<\/span>\n <span class=\"tool-badge\">Gemini<\/span>\n <span class=\"tool-badge\">Perplexity<\/span>\n <span class=\"tool-badge\">Grok<\/span>\n <\/div>\n <\/div>\n\n <div class=\"card-body\">\n <div class=\"section-title-container\">\n <h2 class=\"section-title\">The Prompt<\/h2>\n <button class=\"copy-button\" onclick=\"copyPrompt()\">\ud83d\udccb Copy Prompt<\/button>\n <\/div>\n\n <div class=\"prompt-box\" id=\"promptContent\">You are an AI reliability engineer. Design a hallucination mitigation strategy for this AI system:\n\n<span class=\"placeholder\">[SYSTEM_DESCRIPTION]<\/span> (e.g., \"customer support chatbot\", \"legal contract assistant\", \"clinical summarizer\", \"finance Q&A\", \"developer assistant\")\n\n<span class=\"placeholder\">[KNOWLEDGE_SOURCES]<\/span> (e.g., \"internal KB\", \"public web\", \"PDF policy docs\", \"database\", \"none\")\n\n<span class=\"placeholder\">[RISK_LEVEL]<\/span> (e.g., \"high-stakes\", \"medium\", \"low\")\n\n<span class=\"placeholder\">[OUTPUT_TYPES]<\/span> (e.g., \"answers\", \"summaries\", \"recommendations\", \"citations\", \"calculations\")\n\n<span class=\"placeholder\">[ERROR_TOLERANCE]<\/span> (e.g., \"<0.5% factual errors\", \"minimize harm even if less helpful\")\n\n<span class=\"placeholder\">[CONSTRAINTS]<\/span> (e.g., \"must be fast\", \"limited budget\", \"no internet access\", \"must cite sources\")\n\nUse the R.E.A.L. FRAMEWORK:\n\n**R - Retrieve Ground Truth** \u2192 Prefer grounded answers (RAG, tools, databases)\n**E - Enforce Uncertainty** \u2192 Explicitly separate known vs. unknown, require confidence and caveats\n**A - Answer with Evidence** \u2192 Provide citations, quotes, and traceable reasoning\n**L - Loop with Verification** \u2192 Self-check, cross-check, and human review on risk bands\n\nDELIVER 12 COMPONENTS:\n\n\u2713 1. Hallucination Risk Map (where hallucinations occur, examples)\n\u2713 2. Grounding Strategy (RAG\/tools\/DB queries + how to choose sources)\n\u2713 3. Prompt & Output Constraints (style rules, refusal rules, uncertainty format)\n\u2713 4. Evidence Requirements (citations, quotes, provenance)\n\u2713 5. Verification Pipeline (self-check + second pass + tool verification)\n\u2713 6. Confidence Calibration (thresholds for allow\/review\/refuse)\n\u2713 7. High-Risk Topic Safeguards (medical\/legal\/financial policies)\n\u2713 8. Memory & Context Controls (avoid invented history, session boundaries)\n\u2713 9. Monitoring Metrics (hallucination rate, citation coverage, escalation rate)\n\u2713 10. Incident Response Runbook (SEV levels, containment, fixes)\n\u2713 11. Evaluation Plan (test set, red-team prompts, adversarial cases)\n\u2713 12. 90-Day Implementation Roadmap\n\nOUTPUT FORMAT:\n\n## Risk Map\n\n## Grounding Strategy\n\n## Prompt & Output Constraints\n\n## Evidence Requirements\n\n## Verification Pipeline\n\n## Confidence Calibration\n\n## High-Risk Safeguards\n\n## Memory & Context Controls\n\n## Monitoring Metrics\n\n## Incident Response\n\n## Evaluation Plan\n\n## 90-Day Roadmap\n\nConstraints:\n- Include numeric thresholds (confidence bands) and decision policy\n- Include a citation format and a \u201cno source \u2192 no claim\u201d rule for high-stakes facts\n- Include at least 15 red-team test prompts\n<\/div>\n\n <div class=\"tip-box\"><strong>\ud83d\udca1 Pro Tip:<\/strong> Most hallucinations are \u201cplausible-sounding completions.\u201d Force grounding: if the answer can\u2019t cite a source, it must switch to \u201cunknown \/ here\u2019s how to verify\u201d mode.<\/div>\n\n <div class=\"section-title-container\"><h2 class=\"section-title\">The Logic<\/h2><\/div>\n\n <h3>1. Grounding (RAG\/Tools) Cuts Hallucinations by Shifting From \u201cGuess\u201d to \u201cLook Up\u201d<\/h3>\n <p><strong>WHY IT WORKS:<\/strong> LLMs are trained to continue text; when asked factual questions without grounding, they produce plausible completions even when uncertain. A retrieval or tool step changes the problem: the model becomes a synthesizer of known information rather than an inventor. This is especially effective for policy, product, and domain-specific knowledge where the answer exists in documents. Grounding also improves consistency: repeated questions yield consistent answers because the same sources are used. When implemented with source selection rules and document freshness controls, RAG reduces errors from outdated memory.<\/p>\n <p><strong>EXAMPLE:<\/strong> Customer support: Without grounding, the model invents return policy details (\u201c30 days\u201d) based on generic priors. With RAG, it retrieves the exact policy text (\u201cReturns accepted within 45 days for unused items\u201d) and quotes it. Add \u201cno source \u2192 no claim\u201d rule: if retrieval fails, the model responds with steps to verify (link to policy page, request order details) instead of guessing. In pilots, teams often see a large drop in incorrect policy answers and a rise in \u201cI don\u2019t know yet\u201d responses that route to humans. This trade improves trust and reduces costly escalations.<\/p>\n\n <h3>2. Output Constraints Prevent the Model From Filling Gaps With Fabrication<\/h3>\n <p><strong>WHY IT WORKS:<\/strong> Many hallucinations are caused by ambiguous prompts asking the model to be helpful without specifying boundaries. Output constraints (structure, refusal rules, required uncertainty sections) reduce the degrees of freedom. By forcing the model to separate \u201cVerified\u201d vs. \u201cUnverified\u201d and to state sources, you prevent it from presenting guesses as facts. Constraints also help downstream systems: structured outputs can be checked automatically (e.g., citations present, numbers consistent).<\/p>\n <p><strong>EXAMPLE:<\/strong> Force a template: \u201cAnswer; Evidence (citations + quotes); Confidence; Unknowns; Next verification steps.\u201d Require that every factual claim has a citation. If the model can\u2019t cite, it must place the claim under \u201cUnknowns\u201d and propose verification steps. Add banned behaviors: \u201cDo not invent policies, prices, legal advice, medical dosages, or citations.\u201d These constraints reduce \u201cconfident nonsense\u201d because the model must produce evidence fields. In QA, you can automatically fail outputs that contain numbers with no citation or that cite nonexistent sources. Over time, this reduces the hallucination rate and improves reliability.<\/p>\n\n <h3>3. Verification Pipelines Catch Self-Contradictions and Unsupported Claims<\/h3>\n <p><strong>WHY IT WORKS:<\/strong> A single-pass generation often includes subtle contradictions (dates mismatch, totals wrong) and ungrounded claims. A verification pipeline adds a second \u201ccritic\u201d pass: check citations exist, compare claims to retrieved text, validate calculations, and flag risky statements. This is similar to code review: you reduce defects by adding another structured check. The verification pass can be the same model with a different prompt or a different model to reduce correlated errors. Verification is most valuable when used selectively for high-risk responses, keeping cost manageable.<\/p>\n <p><strong>EXAMPLE:<\/strong> For finance Q&A: Step 1: retrieve relevant SEC filing excerpt and generate answer with citations. Step 2: verifier prompt: \u201cList all factual claims; for each, cite the supporting quote; if missing, mark UNSUPPORTED; check numeric consistency.\u201d Step 3: if any UNSUPPORTED claims in high-stakes categories, either (a) re-run with improved retrieval, (b) downgrade confidence and route to human review. In production, teams often discover that 20\u201340% of initial answers have at least one unsupported claim even if the overall answer seems correct. Verification catches these before users see them, improving trust and reducing costly retractions.<\/p>\n\n <h3>4. Confidence Calibration Enables Safe Automation Without Over-Reviewing Everything<\/h3>\n <p><strong>WHY IT WORKS:<\/strong> \u201cAlways human review\u201d is too expensive; \u201cnever human review\u201d is too risky. Confidence calibration creates a decision policy: low-risk answers can be auto-shipped at high confidence; ambiguous answers route to humans; very low confidence triggers refusal or verification steps. Calibration requires empirical measurement: sample outputs, label correctness, and choose thresholds that meet your error tolerance. This optimizes cost-quality and prevents silent failures in borderline cases.<\/p>\n <p><strong>EXAMPLE:<\/strong> For internal policy assistant: Green: confidence \u2265 0.90 AND \u2265 2 citations \u2192 auto-respond. Yellow: 0.70\u20130.90 OR missing citations \u2192 ask clarifying question or route to human. Red: <0.70 OR any medical\/legal\/financial claim without citation \u2192 refuse and provide verification steps. In pilot, this can cut human review volume by 60\u201380% while keeping factual error rate under 0.5%. Importantly, calibration may differ by topic: product specs might need 0.85, legal advice might need 0.95 plus mandatory citations. This nuance avoids unnecessary review on low-stakes topics while tightening controls where harm is high.<\/p>\n\n <h3>5. High-Risk Safeguards Restrict the Model\u2019s \u201cHelpfulness\u201d in Dangerous Domains<\/h3>\n <p><strong>WHY IT WORKS:<\/strong> In high-stakes domains, even a small error can cause harm. The safest approach is to constrain what the model can do: provide general info, cite official sources, and defer decisions to humans. Safeguards include mandatory citations, refusal rules, and safe alternatives (\u201cI can\u2019t diagnose; consult a professional\u201d). This reduces harmful hallucinations and legal exposure. It also aligns with governance expectations: the system must be designed to avoid giving authoritative-seeming advice where it cannot be trusted.<\/p>\n <p><strong>EXAMPLE:<\/strong> Medical: never provide dosages; always say \u201cconsult clinician,\u201d and cite clinical guidelines if summarizing. Legal: never interpret contracts as binding advice; cite clause text and recommend legal review. Finance: avoid personalized investment advice; cite official filings and provide general risk explanations. Add a \u201chigh-risk query classifier\u201d that detects these topics and forces stricter output template and lower automation thresholds. This design prevents the most damaging hallucinations: confident but wrong prescriptions, legal obligations, or financial claims.<\/p>\n\n <h3>6. Monitoring + Incident Response Makes Reliability Maintainable Over Time<\/h3>\n <p><strong>WHY IT WORKS:<\/strong> Even well-designed systems drift: new docs, changed policies, new product SKUs, new user behavior. Monitoring tracks hallucination rate (via audits), citation coverage, escalation rates, and user complaints. Incident response defines what happens when errors spike: disable features, change prompts, update retrieval, and communicate. This operational discipline turns reliability into an ongoing practice like SRE (site reliability engineering), reducing the chance of public failures and enabling rapid recovery.<\/p>\n <p><strong>EXAMPLE:<\/strong> Define SEV levels: SEV-1: harmful hallucination (legal\/medical\/financial) reported \u2192 immediate containment: disable auto-answer, route to humans, notify owners within 1 hour, publish user notice if needed. SEV-2: citation coverage drop > 10 points week-over-week \u2192 investigate retrieval pipeline. Track weekly: audited factual error rate target <0.5%; citation coverage target >90% for grounded answers; \u201cunknown\u201d response rate should not exceed 25% (balance helpfulness). With these metrics, teams catch regressions early and treat hallucination as an engineering reliability problem, not a vague AI phenomenon.<\/p>\n\n <div class=\"section-title-container\"><h2 class=\"section-title\">Example Output Preview<\/h2><\/div>\n\n <div class=\"example-output\">\n <h4>Sample: Hallucination Mitigation for an Internal HR Policy Assistant<\/h4>\n <p><strong>System:<\/strong> HR chatbot answers employee questions using HR policy PDFs. Risk: medium-high (employment policies). Error tolerance: <0.5% policy inaccuracies.<\/p>\n <p><strong>Grounding:<\/strong> RAG over approved HR policy documents only; freshness check weekly; retrieval top-5 passages; quote mandatory for policy claims.<\/p>\n <p><strong>Constraints:<\/strong> \u201cNo source \u2192 no policy claim.\u201d \u201cIf policy text not found, ask clarifying questions or route to HR.\u201d Output sections: Answer, Evidence (quotes), Confidence, Unknowns, Next Steps.<\/p>\n <p><strong>Verification:<\/strong> Second-pass verifier checks each claim against quotes; rejects unsupported claims; numeric and date consistency check.<\/p>\n <p><strong>Confidence Bands:<\/strong> Green \u22650.90 + \u22652 quotes \u2192 auto-answer. Yellow 0.70\u20130.90 or 1 quote \u2192 ask clarification or create HR ticket. Red <0.70 or missing quotes \u2192 refuse with verification steps.<\/p>\n <p><strong>Pilot Metrics (3,200 Qs):<\/strong> Citation coverage 94%; audited factual error rate 0.4%; HR ticket rate 18%; employee satisfaction 4.6\/5; time saved ~220 HR hours\/month.<\/p>\n <\/div>\n\n <div class=\"section-title-container\"><h2 class=\"section-title\">Prompt Chain Strategy<\/h2><\/div>\n\n <div class=\"chain-step\">\n <h4>Step 1: Design the Mitigation Architecture<\/h4>\n <p><strong>Prompt:<\/strong> Use the main AI Hallucination Mitigation prompt with your system context.<\/p>\n <p><strong>Expected Output:<\/strong> A complete mitigation plan with grounding, constraints, verification, thresholds, monitoring, and a 90-day roadmap.<\/p>\n <\/div>\n\n <div class=\"chain-step\">\n <h4>Step 2: Build the Red-Team Test Suite<\/h4>\n <p><strong>Prompt:<\/strong> \u201cGenerate 50 red-team prompts targeting hallucinations: missing docs, ambiguous questions, outdated policies, trick questions, numbers\/dates, and high-risk domains. Provide expected safe behavior and pass\/fail criteria.\u201d<\/p>\n <p><strong>Expected Output:<\/strong> A repeatable test suite to evaluate improvements and prevent regressions.<\/p>\n <\/div>\n\n <div class=\"chain-step\">\n <h4>Step 3: Implement an Automated Verifier and Monitoring Dashboard<\/h4>\n <p><strong>Prompt:<\/strong> \u201cDesign the verifier prompt + rules engine that checks citations and numeric consistency. Then design dashboards and alert thresholds. Include incident runbooks for SEV-1\/2\/3.\u201d<\/p>\n <p><strong>Expected Output:<\/strong> An operational reliability layer that keeps hallucinations under control in production.<\/p>\n <\/div>\n\n <div class=\"section-title-container\"><h2 class=\"section-title\">Human-in-the-Loop Refinements<\/h2><\/div>\n\n <h3>Maintain a Curated \u201cGold Answers\u201d Set for Critical Questions<\/h3>\n <p>Identify 50\u2013200 high-frequency, high-risk questions and author approved answers with citations. Use them for regression tests and as fallback responses. <strong>Technique:<\/strong> weekly review with policy owners.<\/p>\n\n <h3>Add \u201cClarifying Question First\u201d for Ambiguous Inputs<\/h3>\n <p>Many hallucinations happen when questions are underspecified. Require the model to ask 1\u20133 clarifying questions before answering if retrieval is weak. <strong>Technique:<\/strong> refuse to answer if key parameters missing.<\/p>\n\n <h3>Instrument a \u201cCite-to-Claim Ratio\u201d KPI<\/h3>\n <p>Track number of factual claims per citation. High ratios indicate risk. <strong>Technique:<\/strong> enforce max 2\u20133 claims per citation in policy answers.<\/p>\n\n <h3>Route High-Risk Topics to Specialized Workflows<\/h3>\n <p>Use a classifier to detect legal\/medical\/financial topics and apply stricter templates and thresholds. <strong>Technique:<\/strong> lower automation and enforce human review.<\/p>\n\n <h3>Regularly Refresh Retrieval Sources and Validate Document Freshness<\/h3>\n <p>Outdated docs cause \u201caccurate but wrong\u201d answers. Track document version and update cadence. <strong>Technique:<\/strong> refuse if doc timestamp unknown.<\/p>\n\n <h3>Use User Feedback as a Hallucination Signal<\/h3>\n <p>Collect \u201cincorrect\u201d feedback and triage weekly. <strong>Technique:<\/strong> label top 50 failures\/month and use them as red-team regression tests.<\/p>\n\n <div class=\"footer\">\n <div class=\"footer-stat\"><div class=\"footer-stat-value\">4.9\u2605<\/div><div class=\"footer-stat-label\">Average Rating<\/div><\/div>\n <div class=\"footer-stat\"><div class=\"footer-stat-value\">1,982<\/div><div class=\"footer-stat-label\">Times Copied<\/div><\/div>\n <div class=\"footer-stat\"><div class=\"footer-stat-value\">152<\/div><div class=\"footer-stat-label\">Reviews<\/div><\/div>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n\n <script>\n function copyPrompt(){\n const promptContent=document.getElementById('promptContent').innerText;\n navigator.clipboard.writeText(promptContent).then(()=>{\n const button=document.querySelector('.copy-button');\n const originalText=button.innerHTML;\n button.innerHTML='\u2713 Copied!';\n setTimeout(()=>{button.innerHTML=originalText;},2000);\n }).catch(err=>console.error('Failed to copy text: ',err));\n }\n <\/script>\n<\/body>\n<\/html>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"<p>AI Hallucination Mitigation – AiPro Institute\u2122 AI Hallucination Mitigation AI Hallucination Mitigation AI Safety & Governance \u23f1\ufe0f 30-45 minutes \ud83d\udcca Advanced ChatGPT Claude Gemini Perplexity Grok The Prompt \ud83d\udccb Copy Prompt You are an AI reliability engineer. Design a hallucination mitigation strategy for this AI system: [SYSTEM_DESCRIPTION] (e.g., “customer support chatbot”, “legal contract assistant”, “clinical…<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[170],"tags":[],"class_list":["post-5622","post","type-post","status-publish","format-standard","hentry","category-ai-safety-governance"],"acf":[],"_links":{"self":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts\/5622","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/comments?post=5622"}],"version-history":[{"count":4,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts\/5622\/revisions"}],"predecessor-version":[{"id":5641,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts\/5622\/revisions\/5641"}],"wp:attachment":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/media?parent=5622"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/categories?post=5622"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/tags?post=5622"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

\n\t\t\t\t\t\t

\n\t\t\t\t\t

\n\t\t\t

\n\t\t\t\t\t\t

\n\t\t\t\t\t\n\n\n \n \n AI Hallucination Mitigation - AiPro Institute\u2122<\/title>\n <style>\n *{margin:0;padding:0;box-sizing:border-box}\n body{font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Roboto,'Helvetica Neue',Arial,sans-serif;line-height:1.6;color:#333;background:#fff;padding:2rem 1rem}\n .container{max-width:900px;margin:0 auto}\n .page-title{text-align:center;font-size:2.5rem;font-weight:700;background:linear-gradient(135deg,#667eea 0%,#764ba2 100%);-webkit-background-clip:text;-webkit-text-fill-color:transparent;background-clip:text;margin-bottom:2rem}\n .card{background:#fff;border-radius:12px;box-shadow:0 4px 6px rgba(0,0,0,.1);overflow:hidden;margin-bottom:2rem}\n .card-header{background:linear-gradient(135deg,#667eea 0%,#764ba2 100%);color:#fff;padding:2rem}\n .card-header h1{font-size:2rem;margin-bottom:.5rem}\n .card-header .subtitle{font-size:1.1rem;opacity:.95}\n .meta-badges,.tool-badges{display:flex;gap:.75rem;margin-top:1rem;flex-wrap:wrap}\n .badge{background:rgba(255,255,255,.2);padding:.4rem .9rem;border-radius:20px;font-size:.9rem;backdrop-filter:blur(10px)}\n .tool-badge{background:transparent;border:1px solid rgba(255,255,255,.4);padding:.4rem .9rem;border-radius:20px;font-size:.85rem}\n .card-body{padding:2.5rem}\n .section-title-container{display:flex;justify-content:space-between;align-items:center;margin:2.5rem 0 1.25rem 0}\n .section-title-container:first-child{margin-top:0}\n .section-title{font-size:1.75rem;color:#764ba2;border-left:4px solid #764ba2;padding-left:1rem;margin:0}\n .copy-button{background:linear-gradient(135deg,#667eea 0%,#764ba2 100%);color:#fff;border:none;padding:.6rem 1.5rem;border-radius:6px;cursor:pointer;font-size:.95rem;font-weight:500;transition:opacity .3s}\n .copy-button:hover{opacity:.9}\n .prompt-box{background:#f8f9fa;border:1px solid #dee2e6;border-radius:8px;padding:1.5rem;margin:1.25rem 0;font-family:'Courier New',monospace;font-size:.95rem;line-height:1.6;white-space:pre-wrap;overflow-x:auto}\n .placeholder{color:#fd7e14;font-weight:bold}\n .tip-box{background:#fff9e6;border-left:4px solid #ffc107;padding:1.25rem;margin:1.25rem 0;border-radius:4px}\n .tip-box strong{color:#f57c00}\n h3{color:#764ba2;font-size:1.35rem;margin:2rem 0 1rem 0}\n p{margin-bottom:1rem;line-height:1.8}\n ul,ol{margin-left:2rem;margin-bottom:1rem}\n li{margin-bottom:.5rem;line-height:1.8}\n .example-output{background:#f0f8ff;border:2px solid #4a90e2;border-radius:8px;padding:1.5rem;margin:1.25rem 0}\n .example-output h4{color:#4a90e2;margin-bottom:1rem}\n .chain-step{background:#f8f9fa;border-left:4px solid #667eea;padding:1.5rem;margin:1.5rem 0;border-radius:4px}\n .chain-step h4{color:#667eea;margin-bottom:.75rem}\n .footer{background:#f8f9fa;padding:2rem;margin-top:2rem;border-radius:8px;display:flex;justify-content:space-around;align-items:center;flex-wrap:wrap;gap:1.5rem}\n .footer-stat{text-align:center}\n .footer-stat-value{font-size:1.75rem;font-weight:700;color:#764ba2}\n .footer-stat-label{color:#666;font-size:.95rem}\n @media (max-width:768px){.page-title{font-size:1.75rem}.card-header h1{font-size:1.5rem}.card-body{padding:1.5rem}.section-title{font-size:1.35rem}.section-title-container{flex-direction:column;align-items:flex-start;gap:1rem}.footer{flex-direction:column}}\n <\/style>\n<\/head>\n<body>\n <div class=\"container\">\n <h1 class=\"page-title\">AI Hallucination Mitigation<\/h1>\n\n <div class=\"card\">\n <div class=\"card-header\">\n <h1>AI Hallucination Mitigation<\/h1>\n <p class=\"subtitle\">AI Safety & Governance<\/p>\n <div class=\"meta-badges\">\n <span class=\"badge\">\u23f1\ufe0f 30-45 minutes<\/span>\n <span class=\"badge\">\ud83d\udcca Advanced<\/span>\n <\/div>\n <div class=\"tool-badges\">\n <span class=\"tool-badge\">ChatGPT<\/span>\n <span class=\"tool-badge\">Claude<\/span>\n <span class=\"tool-badge\">Gemini<\/span>\n <span class=\"tool-badge\">Perplexity<\/span>\n <span class=\"tool-badge\">Grok<\/span>\n <\/div>\n <\/div>\n\n <div class=\"card-body\">\n <div class=\"section-title-container\">\n <h2 class=\"section-title\">The Prompt<\/h2>\n <button class=\"copy-button\" onclick=\"copyPrompt()\">\ud83d\udccb Copy Prompt<\/button>\n <\/div>\n\n <div class=\"prompt-box\" id=\"promptContent\">You are an AI reliability engineer. Design a hallucination mitigation strategy for this AI system:\n\n<span class=\"placeholder\">[SYSTEM_DESCRIPTION]<\/span> (e.g., \"customer support chatbot\", \"legal contract assistant\", \"clinical summarizer\", \"finance Q&A\", \"developer assistant\")\n\n<span class=\"placeholder\">[KNOWLEDGE_SOURCES]<\/span> (e.g., \"internal KB\", \"public web\", \"PDF policy docs\", \"database\", \"none\")\n\n<span class=\"placeholder\">[RISK_LEVEL]<\/span> (e.g., \"high-stakes\", \"medium\", \"low\")\n\n<span class=\"placeholder\">[OUTPUT_TYPES]<\/span> (e.g., \"answers\", \"summaries\", \"recommendations\", \"citations\", \"calculations\")\n\n<span class=\"placeholder\">[ERROR_TOLERANCE]<\/span> (e.g., \"<0.5% factual errors\", \"minimize harm even if less helpful\")\n\n<span class=\"placeholder\">[CONSTRAINTS]<\/span> (e.g., \"must be fast\", \"limited budget\", \"no internet access\", \"must cite sources\")\n\nUse the R.E.A.L. FRAMEWORK:\n\n**R - Retrieve Ground Truth** \u2192 Prefer grounded answers (RAG, tools, databases)\n**E - Enforce Uncertainty** \u2192 Explicitly separate known vs. unknown, require confidence and caveats\n**A - Answer with Evidence** \u2192 Provide citations, quotes, and traceable reasoning\n**L - Loop with Verification** \u2192 Self-check, cross-check, and human review on risk bands\n\nDELIVER 12 COMPONENTS:\n\n\u2713 1. Hallucination Risk Map (where hallucinations occur, examples)\n\u2713 2. Grounding Strategy (RAG\/tools\/DB queries + how to choose sources)\n\u2713 3. Prompt & Output Constraints (style rules, refusal rules, uncertainty format)\n\u2713 4. Evidence Requirements (citations, quotes, provenance)\n\u2713 5. Verification Pipeline (self-check + second pass + tool verification)\n\u2713 6. Confidence Calibration (thresholds for allow\/review\/refuse)\n\u2713 7. High-Risk Topic Safeguards (medical\/legal\/financial policies)\n\u2713 8. Memory & Context Controls (avoid invented history, session boundaries)\n\u2713 9. Monitoring Metrics (hallucination rate, citation coverage, escalation rate)\n\u2713 10. Incident Response Runbook (SEV levels, containment, fixes)\n\u2713 11. Evaluation Plan (test set, red-team prompts, adversarial cases)\n\u2713 12. 90-Day Implementation Roadmap\n\nOUTPUT FORMAT:\n\n## Risk Map\n\n## Grounding Strategy\n\n## Prompt & Output Constraints\n\n## Evidence Requirements\n\n## Verification Pipeline\n\n## Confidence Calibration\n\n## High-Risk Safeguards\n\n## Memory & Context Controls\n\n## Monitoring Metrics\n\n## Incident Response\n\n## Evaluation Plan\n\n## 90-Day Roadmap\n\nConstraints:\n- Include numeric thresholds (confidence bands) and decision policy\n- Include a citation format and a \u201cno source \u2192 no claim\u201d rule for high-stakes facts\n- Include at least 15 red-team test prompts\n<\/div>\n\n <div class=\"tip-box\"><strong>\ud83d\udca1 Pro Tip:<\/strong> Most hallucinations are \u201cplausible-sounding completions.\u201d Force grounding: if the answer can\u2019t cite a source, it must switch to \u201cunknown \/ here\u2019s how to verify\u201d mode.<\/div>\n\n <div class=\"section-title-container\"><h2 class=\"section-title\">The Logic<\/h2><\/div>\n\n <h3>1. Grounding (RAG\/Tools) Cuts Hallucinations by Shifting From \u201cGuess\u201d to \u201cLook Up\u201d<\/h3>\n <p><strong>WHY IT WORKS:<\/strong> LLMs are trained to continue text; when asked factual questions without grounding, they produce plausible completions even when uncertain. A retrieval or tool step changes the problem: the model becomes a synthesizer of known information rather than an inventor. This is especially effective for policy, product, and domain-specific knowledge where the answer exists in documents. Grounding also improves consistency: repeated questions yield consistent answers because the same sources are used. When implemented with source selection rules and document freshness controls, RAG reduces errors from outdated memory.<\/p>\n <p><strong>EXAMPLE:<\/strong> Customer support: Without grounding, the model invents return policy details (\u201c30 days\u201d) based on generic priors. With RAG, it retrieves the exact policy text (\u201cReturns accepted within 45 days for unused items\u201d) and quotes it. Add \u201cno source \u2192 no claim\u201d rule: if retrieval fails, the model responds with steps to verify (link to policy page, request order details) instead of guessing. In pilots, teams often see a large drop in incorrect policy answers and a rise in \u201cI don\u2019t know yet\u201d responses that route to humans. This trade improves trust and reduces costly escalations.<\/p>\n\n <h3>2. Output Constraints Prevent the Model From Filling Gaps With Fabrication<\/h3>\n <p><strong>WHY IT WORKS:<\/strong> Many hallucinations are caused by ambiguous prompts asking the model to be helpful without specifying boundaries. Output constraints (structure, refusal rules, required uncertainty sections) reduce the degrees of freedom. By forcing the model to separate \u201cVerified\u201d vs. \u201cUnverified\u201d and to state sources, you prevent it from presenting guesses as facts. Constraints also help downstream systems: structured outputs can be checked automatically (e.g., citations present, numbers consistent).<\/p>\n <p><strong>EXAMPLE:<\/strong> Force a template: \u201cAnswer; Evidence (citations + quotes); Confidence; Unknowns; Next verification steps.\u201d Require that every factual claim has a citation. If the model can\u2019t cite, it must place the claim under \u201cUnknowns\u201d and propose verification steps. Add banned behaviors: \u201cDo not invent policies, prices, legal advice, medical dosages, or citations.\u201d These constraints reduce \u201cconfident nonsense\u201d because the model must produce evidence fields. In QA, you can automatically fail outputs that contain numbers with no citation or that cite nonexistent sources. Over time, this reduces the hallucination rate and improves reliability.<\/p>\n\n <h3>3. Verification Pipelines Catch Self-Contradictions and Unsupported Claims<\/h3>\n <p><strong>WHY IT WORKS:<\/strong> A single-pass generation often includes subtle contradictions (dates mismatch, totals wrong) and ungrounded claims. A verification pipeline adds a second \u201ccritic\u201d pass: check citations exist, compare claims to retrieved text, validate calculations, and flag risky statements. This is similar to code review: you reduce defects by adding another structured check. The verification pass can be the same model with a different prompt or a different model to reduce correlated errors. Verification is most valuable when used selectively for high-risk responses, keeping cost manageable.<\/p>\n <p><strong>EXAMPLE:<\/strong> For finance Q&A: Step 1: retrieve relevant SEC filing excerpt and generate answer with citations. Step 2: verifier prompt: \u201cList all factual claims; for each, cite the supporting quote; if missing, mark UNSUPPORTED; check numeric consistency.\u201d Step 3: if any UNSUPPORTED claims in high-stakes categories, either (a) re-run with improved retrieval, (b) downgrade confidence and route to human review. In production, teams often discover that 20\u201340% of initial answers have at least one unsupported claim even if the overall answer seems correct. Verification catches these before users see them, improving trust and reducing costly retractions.<\/p>\n\n <h3>4. Confidence Calibration Enables Safe Automation Without Over-Reviewing Everything<\/h3>\n <p><strong>WHY IT WORKS:<\/strong> \u201cAlways human review\u201d is too expensive; \u201cnever human review\u201d is too risky. Confidence calibration creates a decision policy: low-risk answers can be auto-shipped at high confidence; ambiguous answers route to humans; very low confidence triggers refusal or verification steps. Calibration requires empirical measurement: sample outputs, label correctness, and choose thresholds that meet your error tolerance. This optimizes cost-quality and prevents silent failures in borderline cases.<\/p>\n <p><strong>EXAMPLE:<\/strong> For internal policy assistant: Green: confidence \u2265 0.90 AND \u2265 2 citations \u2192 auto-respond. Yellow: 0.70\u20130.90 OR missing citations \u2192 ask clarifying question or route to human. Red: <0.70 OR any medical\/legal\/financial claim without citation \u2192 refuse and provide verification steps. In pilot, this can cut human review volume by 60\u201380% while keeping factual error rate under 0.5%. Importantly, calibration may differ by topic: product specs might need 0.85, legal advice might need 0.95 plus mandatory citations. This nuance avoids unnecessary review on low-stakes topics while tightening controls where harm is high.<\/p>\n\n <h3>5. High-Risk Safeguards Restrict the Model\u2019s \u201cHelpfulness\u201d in Dangerous Domains<\/h3>\n <p><strong>WHY IT WORKS:<\/strong> In high-stakes domains, even a small error can cause harm. The safest approach is to constrain what the model can do: provide general info, cite official sources, and defer decisions to humans. Safeguards include mandatory citations, refusal rules, and safe alternatives (\u201cI can\u2019t diagnose; consult a professional\u201d). This reduces harmful hallucinations and legal exposure. It also aligns with governance expectations: the system must be designed to avoid giving authoritative-seeming advice where it cannot be trusted.<\/p>\n <p><strong>EXAMPLE:<\/strong> Medical: never provide dosages; always say \u201cconsult clinician,\u201d and cite clinical guidelines if summarizing. Legal: never interpret contracts as binding advice; cite clause text and recommend legal review. Finance: avoid personalized investment advice; cite official filings and provide general risk explanations. Add a \u201chigh-risk query classifier\u201d that detects these topics and forces stricter output template and lower automation thresholds. This design prevents the most damaging hallucinations: confident but wrong prescriptions, legal obligations, or financial claims.<\/p>\n\n <h3>6. Monitoring + Incident Response Makes Reliability Maintainable Over Time<\/h3>\n <p><strong>WHY IT WORKS:<\/strong> Even well-designed systems drift: new docs, changed policies, new product SKUs, new user behavior. Monitoring tracks hallucination rate (via audits), citation coverage, escalation rates, and user complaints. Incident response defines what happens when errors spike: disable features, change prompts, update retrieval, and communicate. This operational discipline turns reliability into an ongoing practice like SRE (site reliability engineering), reducing the chance of public failures and enabling rapid recovery.<\/p>\n <p><strong>EXAMPLE:<\/strong> Define SEV levels: SEV-1: harmful hallucination (legal\/medical\/financial) reported \u2192 immediate containment: disable auto-answer, route to humans, notify owners within 1 hour, publish user notice if needed. SEV-2: citation coverage drop > 10 points week-over-week \u2192 investigate retrieval pipeline. Track weekly: audited factual error rate target <0.5%; citation coverage target >90% for grounded answers; \u201cunknown\u201d response rate should not exceed 25% (balance helpfulness). With these metrics, teams catch regressions early and treat hallucination as an engineering reliability problem, not a vague AI phenomenon.<\/p>\n\n <div class=\"section-title-container\"><h2 class=\"section-title\">Example Output Preview<\/h2><\/div>\n\n <div class=\"example-output\">\n <h4>Sample: Hallucination Mitigation for an Internal HR Policy Assistant<\/h4>\n <p><strong>System:<\/strong> HR chatbot answers employee questions using HR policy PDFs. Risk: medium-high (employment policies). Error tolerance: <0.5% policy inaccuracies.<\/p>\n <p><strong>Grounding:<\/strong> RAG over approved HR policy documents only; freshness check weekly; retrieval top-5 passages; quote mandatory for policy claims.<\/p>\n <p><strong>Constraints:<\/strong> \u201cNo source \u2192 no policy claim.\u201d \u201cIf policy text not found, ask clarifying questions or route to HR.\u201d Output sections: Answer, Evidence (quotes), Confidence, Unknowns, Next Steps.<\/p>\n <p><strong>Verification:<\/strong> Second-pass verifier checks each claim against quotes; rejects unsupported claims; numeric and date consistency check.<\/p>\n <p><strong>Confidence Bands:<\/strong> Green \u22650.90 + \u22652 quotes \u2192 auto-answer. Yellow 0.70\u20130.90 or 1 quote \u2192 ask clarification or create HR ticket. Red <0.70 or missing quotes \u2192 refuse with verification steps.<\/p>\n <p><strong>Pilot Metrics (3,200 Qs):<\/strong> Citation coverage 94%; audited factual error rate 0.4%; HR ticket rate 18%; employee satisfaction 4.6\/5; time saved ~220 HR hours\/month.<\/p>\n <\/div>\n\n <div class=\"section-title-container\"><h2 class=\"section-title\">Prompt Chain Strategy<\/h2><\/div>\n\n <div class=\"chain-step\">\n <h4>Step 1: Design the Mitigation Architecture<\/h4>\n <p><strong>Prompt:<\/strong> Use the main AI Hallucination Mitigation prompt with your system context.<\/p>\n <p><strong>Expected Output:<\/strong> A complete mitigation plan with grounding, constraints, verification, thresholds, monitoring, and a 90-day roadmap.<\/p>\n <\/div>\n\n <div class=\"chain-step\">\n <h4>Step 2: Build the Red-Team Test Suite<\/h4>\n <p><strong>Prompt:<\/strong> \u201cGenerate 50 red-team prompts targeting hallucinations: missing docs, ambiguous questions, outdated policies, trick questions, numbers\/dates, and high-risk domains. Provide expected safe behavior and pass\/fail criteria.\u201d<\/p>\n <p><strong>Expected Output:<\/strong> A repeatable test suite to evaluate improvements and prevent regressions.<\/p>\n <\/div>\n\n <div class=\"chain-step\">\n <h4>Step 3: Implement an Automated Verifier and Monitoring Dashboard<\/h4>\n <p><strong>Prompt:<\/strong> \u201cDesign the verifier prompt + rules engine that checks citations and numeric consistency. Then design dashboards and alert thresholds. Include incident runbooks for SEV-1\/2\/3.\u201d<\/p>\n <p><strong>Expected Output:<\/strong> An operational reliability layer that keeps hallucinations under control in production.<\/p>\n <\/div>\n\n <div class=\"section-title-container\"><h2 class=\"section-title\">Human-in-the-Loop Refinements<\/h2><\/div>\n\n <h3>Maintain a Curated \u201cGold Answers\u201d Set for Critical Questions<\/h3>\n <p>Identify 50\u2013200 high-frequency, high-risk questions and author approved answers with citations. Use them for regression tests and as fallback responses. <strong>Technique:<\/strong> weekly review with policy owners.<\/p>\n\n <h3>Add \u201cClarifying Question First\u201d for Ambiguous Inputs<\/h3>\n <p>Many hallucinations happen when questions are underspecified. Require the model to ask 1\u20133 clarifying questions before answering if retrieval is weak. <strong>Technique:<\/strong> refuse to answer if key parameters missing.<\/p>\n\n <h3>Instrument a \u201cCite-to-Claim Ratio\u201d KPI<\/h3>\n <p>Track number of factual claims per citation. High ratios indicate risk. <strong>Technique:<\/strong> enforce max 2\u20133 claims per citation in policy answers.<\/p>\n\n <h3>Route High-Risk Topics to Specialized Workflows<\/h3>\n <p>Use a classifier to detect legal\/medical\/financial topics and apply stricter templates and thresholds. <strong>Technique:<\/strong> lower automation and enforce human review.<\/p>\n\n <h3>Regularly Refresh Retrieval Sources and Validate Document Freshness<\/h3>\n <p>Outdated docs cause \u201caccurate but wrong\u201d answers. Track document version and update cadence. <strong>Technique:<\/strong> refuse if doc timestamp unknown.<\/p>\n\n <h3>Use User Feedback as a Hallucination Signal<\/h3>\n <p>Collect \u201cincorrect\u201d feedback and triage weekly. <strong>Technique:<\/strong> label top 50 failures\/month and use them as red-team regression tests.<\/p>\n\n <div class=\"footer\">\n <div class=\"footer-stat\"><div class=\"footer-stat-value\">4.9\u2605<\/div><div class=\"footer-stat-label\">Average Rating<\/div><\/div>\n <div class=\"footer-stat\"><div class=\"footer-stat-value\">1,982<\/div><div class=\"footer-stat-label\">Times Copied<\/div><\/div>\n <div class=\"footer-stat\"><div class=\"footer-stat-value\">152<\/div><div class=\"footer-stat-label\">Reviews<\/div><\/div>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n\n <script>\n function copyPrompt(){\n const promptContent=document.getElementById('promptContent').innerText;\n navigator.clipboard.writeText(promptContent).then(()=>{\n const button=document.querySelector('.copy-button');\n const originalText=button.innerHTML;\n button.innerHTML='\u2713 Copied!';\n setTimeout(()=>{button.innerHTML=originalText;},2000);\n }).catch(err=>console.error('Failed to copy text: ',err));\n }\n <\/script>\n<\/body>\n<\/html>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"<p>AI Hallucination Mitigation – AiPro Institute\u2122 AI Hallucination Mitigation AI Hallucination Mitigation AI Safety & Governance \u23f1\ufe0f 30-45 minutes \ud83d\udcca Advanced ChatGPT Claude Gemini Perplexity Grok The Prompt \ud83d\udccb Copy Prompt You are an AI reliability engineer. Design a hallucination mitigation strategy for this AI system: [SYSTEM_DESCRIPTION] (e.g., “customer support chatbot”, “legal contract assistant”, “clinical…<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[170],"tags":[],"class_list":["post-5622","post","type-post","status-publish","format-standard","hentry","category-ai-safety-governance"],"acf":[],"_links":{"self":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts\/5622","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/comments?post=5622"}],"version-history":[{"count":4,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts\/5622\/revisions"}],"predecessor-version":[{"id":5641,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts\/5622\/revisions\/5641"}],"wp:attachment":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/media?parent=5622"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/categories?post=5622"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/tags?post=5622"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}