<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="https://pku-pillar-group.github.io/feed.xml" rel="self" type="application/atom+xml"/><link href="https://pku-pillar-group.github.io/" rel="alternate" type="text/html" hreflang="en"/><updated>2026-09-05T06:53:32+00:00</updated><id>https://pku-pillar-group.github.io/feed.xml</id><title type="html">PILLAR Group</title><subtitle>The PILLAR Group is a natural language processing research lab at Peking University. We study large language models, reasoning, LLM agents, and multilingual NLP. </subtitle><entry><title type="html">Welcome to Lab Notes</title><link href="https://pku-pillar-group.github.io/blog/2025/welcome-to-lab-notes/" rel="alternate" type="text/html" title="Welcome to Lab Notes"/><published>2025-09-01T01:00:00+00:00</published><updated>2025-09-01T01:00:00+00:00</updated><id>https://pku-pillar-group.github.io/blog/2025/welcome-to-lab-notes</id><content type="html" xml:base="https://pku-pillar-group.github.io/blog/2025/welcome-to-lab-notes/"><![CDATA[<p>Welcome to <strong>Lab Notes</strong>, the blog of the PILLAR Group at Peking University.</p> <p>We plan to use this space for informal write-ups that do not fit into papers:</p> <ul> <li><strong>Paper deep-dives</strong> — behind-the-scenes details, ablations, and negative results from our published work</li> <li><strong>Tutorials and reading notes</strong> — on topics like large language models, reasoning, and agents</li> <li><strong>Lab updates</strong> — new members, talks, and open-source releases</li> </ul> <p>Stay tuned — and if you are interested in working with us, check out the <a href="/join/">join us</a> page.</p>]]></content><author><name></name></author><category term="news"/><category term="announcement"/><summary type="html"><![CDATA[why we are starting a blog, and what to expect]]></summary></entry><entry><title type="html">A Practical Checklist for Evaluating LLM Reasoning</title><link href="https://pku-pillar-group.github.io/blog/2025/evaluating-llm-reasoning/" rel="alternate" type="text/html" title="A Practical Checklist for Evaluating LLM Reasoning"/><published>2025-08-20T01:00:00+00:00</published><updated>2025-08-20T01:00:00+00:00</updated><id>https://pku-pillar-group.github.io/blog/2025/evaluating-llm-reasoning</id><content type="html" xml:base="https://pku-pillar-group.github.io/blog/2025/evaluating-llm-reasoning/"><![CDATA[<p>Evaluating reasoning in large language models is trickier than it looks. Here is a checklist we have found useful in our own projects.</p> <h2 id="1-report-more-than-accuracy">1. Report more than accuracy</h2> <p>Pass@1 alone hides a lot. Pair it with pass@k, self-consistency over multiple samples, and variance across seeds.</p> <h2 id="2-watch-for-data-contamination">2. Watch for data contamination</h2> <p>If the benchmark is public, assume it is in the training data. Prefer held-out or newly constructed test sets, and report perplexity-based contamination checks where possible.</p> <h2 id="3-separate-reasoning-from-retrieval">3. Separate reasoning from retrieval</h2> <p>A model that answers correctly may be reciting, not reasoning. Include adversarial variants — same question, perturbed numbers or entities — to test whether the reasoning chain actually transfers.</p> <h2 id="4-check-the-chain-not-just-the-answer">4. Check the chain, not just the answer</h2> <p>Final-answer agreement between chain-of-thought and direct answering can reveal when the rationale is post-hoc. Report both.</p> <p><em>This is placeholder content — replace it with a real post.</em></p>]]></content><author><name></name></author><category term="tutorials"/><category term="evaluation"/><category term="reasoning"/><category term="llm"/><summary type="html"><![CDATA[lessons we learned from benchmarking reasoning abilities of large language models]]></summary></entry></feed>