<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>In-Context Learning on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/in-context-learning/</link><description>Recent content in In-Context Learning on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 31 Oct 2025 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/in-context-learning/index.xml" rel="self" type="application/rss+xml"/><item><title>NLP (7): Prompt Engineering and In-Context Learning</title><link>https://www.chenk.top/en/nlp/prompt-engineering-icl/</link><pubDate>Fri, 31 Oct 2025 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/nlp/prompt-engineering-icl/</guid><description>&lt;p>The same model can produce a sharp answer or a confident hallucination. The difference lies in the framing, not the weights. A vague request like &lt;em>&amp;ldquo;analyze this text&amp;rdquo;&lt;/em> yields a generic summary; a prompt with a role, two clear examples, and a strict output schema produces something a parser can use. &lt;strong>Prompt engineering turns that gap into a repeatable system, not just a lucky shot.&lt;/strong>&lt;/p>
&lt;p>In-Context Learning (ICL) is the mechanism that makes this work. When you include a few examples in the prompt, the model doesn&amp;rsquo;t retrain; it conditions its forward pass on those examples and effectively &lt;em>infers a task&lt;/em> from them. Understanding ICL&amp;rsquo;s capabilities and limitations separates a developer who struggles with the model from one who guides it.&lt;/p></description></item></channel></rss>