Pith. sign in

REVIEW 3 major objections 4 minor 2 cited by

HybGRAG: Hybrid Retrieval-Augmented Generation on Textual and Relational Knowledge Bases

T0 review · 3 major / 4 minor · reviewed 2026-08-11 · deepseek-v4-flash

Pith's one-line read HybGRAG claims that hybrid question answering over semi-structured knowledge bases is best solved by a retriever bank and a critic module that iteratively refines question routing, reporting an average relative Hit@1 gain of 51% over…

desk verdict Strong system paper with a real contribution and a solid empirical case, but the headline 51% gain is inflated by a label-dependent disambiguation step and needs independent replication before the exact numbers are trusted. read the letter →

arxiv 2412.16311 v2 pith:Q4TC5H6Y submitted 2024-12-20 cs.LG cs.AIcs.IR

classification cs.LGcs.AIcs.IR
keywords hybridquestionansweringretrieval-augmentedgenerationgraphRAGsemi-structuredknowledgebaseself-reflectionLLMagentsretrievalroutingcriticmodule
verification ladder T0 review T1 audit T2 compute T3 formal

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The reading

HybGRAG sets out to solve hybrid question answering over semi-structured knowledge bases, where answering a question requires both the textual content of documents and the relational structure of the knowledge graph that connects those documents. The paper argues that existing retrieval methods fail because they use only one source of evidence, and that large language models often misclassify the textual part of a question as a relational one on the first attempt. To fix this, it proposes a retriever bank that routes each question to text or hybrid retrieval, and a critic module that validates the retrieved documents and, when they are wrong, issues corrective feedback so the router can redo its routing. On the STARK benchmark the method reports Hit@1 of 0.654 on the academic set and 0.286 on the precision-medicine set, an average relative improvement of 51% over the compared baselines, and the same design transfers to end-to-end retrieval-augmented generation on the CRAG benchmark.

What carries the argument

The retriever bank and critic module constitute the central machinery. The retriever bank's router takes the question, entity types, relation types, and corrective feedback, and outputs a module selection along with topic entities $\hat{E}_t$ and useful relations $\hat{R}_t$; the text module is vector similarity search over documents, while the hybrid module extracts the ego-graph around the topic entities restricted to the useful relations and then ranks the entities' documents by vector similarity, using the intersection when several ego-graphs are extracted. The critic module splits into a validator that judges, with verbalized reasoning paths as context, whether the retrieved documents satisfy the question, and a commenter that, when validation fails, generates corrective feedback based on in-context examples of successful refinements. The loop iterates until the validator accepts or a maximum iteration count is reached, and this is what lets the system correct its own routing.

What would settle it

A direct check is to run HybGRAG on a held-out set of hybrid questions while logging the router's extracted entities, the validator's accept/reject decisions, and the final answer. If the correct document is already in the first retrieval for most questions but the validator still rejects it, or if the validator accepts incorrect documents as often after refinement as before, then the claimed mechanism—a critic that fixes routing errors—is not what produces the Hit@1 gain. A cheaper version: replace the commenter's corrective feedback with random error-type feedback; if the Hit@1 gap between HybGRAG and its no-critic hybrid module does not largely disappear, the critic is not the driver.

Watch

Extended reading notes

Core claim

The paper's central claim is that hybrid question answering decomposes into two tractable challenges and that each has a dedicated remedy. Challenge 1 is that useful answers live in the non-overlapping strengths of text and graph retrieval; the remedy is a retriever bank whose router decides, per question, whether to use a pure text module or a hybrid module that starts from identified topic entities and useful relations, extracts the relevant ego-graph, and then ranks the associated documents by vector similarity to the question. Challenge 2 is that an LLM asked to do this routing often labels a textual aspect as a relational one, so the first extraction is wrong; the remedy is a critic module that separates validation from commenting, giving the router concrete corrective feedback such as “this entity is incorrect, remove it” rather than a vague re-prompt. The paper reports that this two-module design outperforms all compared RAG, graph-RAG, agentic, and self-reflective baselines on STARK, and that the hybrid retrieval module alone already beats the best baseline, with the critic adding a further substantial gain.

Load-bearing premise

The load-bearing premise is that the LLM that decides what to retrieve and the LLM that checks the retrieved answer are reliable enough that repeating the retrieve-and-check loop homes in on the right answer; the paper reports only final accuracy, not how often those two steps make mistakes.

Editorial extensions

If this is right

  • Unified coverage: the same system handles textual, relational, and hybrid questions, so an application no longer needs separate retrieval pipelines for documents and knowledge graphs.
  • Self-correction without fine-tuning: replacing a single self-reflecting LLM with a validator/commenter split yields better refinements, and the paper's ablation shows the full multi-agent design beats single-agent routing on Hit@1.
  • Cost-effective gains: the hybrid retrieval module needs only about 2 API calls per question and still improves Hit@1 by 24% over the strongest baseline, while the full HybGRAG uses at most about 14 calls, versus hundreds for training-based alternatives.
  • End-to-end answer quality: on CRAG, the retrieval gains translate into higher answer accuracy and lower hallucination and missing-answer rates under two different generator LLMs.
  • Interpretable failure tracking: the refinement path records what was extracted, why it was rejected, and what changed, giving a chain-of-thought-like audit trail for each answer.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

  • The success of the critic module suggests that measuring validator and commenter accuracy in isolation on held-out routing steps would be a good predictor of transfer; the paper leaves that measurement implicit, reporting only end-task Hit@1.
  • The retriever bank is a plug-and-play template: swapping the ego-graph extractor for Personalized PageRank or the ranker for a cross-encoder, which the Limitations section names as unexplored, is a natural next test that should preserve most of the gain if the mechanism is really the router–critic loop.
  • Because STARK-Prime performance is lower than STARK-MAG, the method's advantage may shrink on domains with harder entity ambiguity or less complete knowledge graphs; a stress test varying KG density or entity-name overlap would reveal where the critic saturates.
  • The corrective-feedback format could be reused as a fine-tuning dataset: the paper's in-context examples are verified by ground truth but not used as training labels, and converting them into supervised training data is a direct extension.
Share X Bluesky LinkedIn Reddit HN

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Referee Report

3 major / 4 minor

Summary. The paper proposes HybGRAG, a retrieval-augmented generation framework for hybrid question answering (HQA) over semi-structured knowledge bases (SKBs), where questions require both textual and relational information. HybGRAG combines a retriever bank (a text retrieval module, a hybrid retrieval module, and an LLM router) with a critic module (an LLM validator and commenter) that iteratively refines the router's action based on corrective feedback. The authors report experiments on the STARK and CRAG benchmarks, claiming an average relative Hit@1 improvement of 51% over baselines on STARK, and also present ablations, cost analysis, and illustrative refinement paths. The central claim is that HybGRAG outperforms existing RAG/GRAG and agentic baselines on HQA.

Significance. If the reported results are trustworthy, the paper makes a useful practical contribution: it is the only evaluated method that explicitly targets hybrid questions in SKBs, and its modular design (retriever bank plus critic) is simple and interpretable. A notable strength is that the proposed hybrid retrieval module alone beats the AVATAR baseline, and HybGRAG achieves this while using Claude 3 Sonnet as the base model, even though several baselines use the more capable Claude 3 Opus. The paper also provides a reasonable cost analysis and concrete examples of the refinement process. However, the central empirical claim is weakened by a label-dependent entity disambiguation step in the evaluation (Appendix C.1.1), which uses ground-truth answers at inference time. This issue directly affects the magnitude of the reported gains and must be addressed before the results can be accepted as stated.

major comments (3)
  1. [Appendix C.1.1] The evaluation protocol for STARK contains a label-dependent disambiguation step: when multiple entities share the same extracted name, 'we select the entity that has the answer in its one-hop neighborhood for disambiguation.' This uses ground-truth answers at inference time and therefore inflates Hit@1. The appendix reports this affects 3.83% of STARK-MAG test questions (about 102 of 2665) and 0.07% of STARK-PRIME questions. Since the hybrid retrieval module's Hit@1 margin over AVATAR on MAG is only about 0.059 (0.5028 vs. 0.4436), the potential inflation of up to 0.038 could account for a large fraction of that advantage, even if the full HybGRAG margin over AVATAR (about 0.21) is more robust. The authors should rerun the evaluation without any label-dependent choice, or replace it with an unsupervised disambiguation method, and report the resulting numbers. Without this, the headline 51% relative improvement is not trustworthy as a measure of the retrieval method's true performance.
  2. [Section 4.1, Table 5] All reported STARK and CRAG results are from single runs with no error bars, confidence intervals, or significance tests. The abstract and Section 4.1.1 describe 'significant performance gains,' but the term 'significant' is not supported statistically. Because the system relies on stochastic LLM components (router, validator, commenter) and randomly selected in-context examples, repeated runs or bootstrap resampling should be reported to establish that the observed margins are not noise. This is particularly important for the smaller margins (e.g., between HybGRAG and the hybrid retrieval module on some CRAG metrics).
  3. [Appendix C.1.2 and Section 4.1.2] There is a contradiction about access to Claude 3 Opus. Section 4.1.2 states 'Although we do not have access to Claude 3 Opus,' while Appendix C.1.2 states that ReAct, Reflexion, AVATAR, and VSS with LLM reranker 'use Claude 3 Opus.' If the authors could not access Opus, these baseline results must have been taken from prior work or obtained through another route; if so, the comparison protocol may differ in prompts, retrieval code, or evaluation settings. The authors should clarify how the Opus baseline numbers were produced and confirm that all methods were evaluated under the same conditions, or rerun the baselines with an accessible backbone.
minor comments (4)
  1. [Throughout] The benchmark name is written inconsistently as 'STARK' and 'STaRK'; please use a single spelling throughout.
  2. [Figure 2] The labels '21% Higher' and '10% Higher' in Figure 2 are unclear; specify whether these are absolute or relative improvements and to which baseline they refer.
  3. [Appendix C.1.1] The statement that ambiguous entity names 'rarely happen' is contradicted by the reported 3.83% on STARK-MAG; please rephrase and report the exact number of affected questions.
  4. [Algorithm 1] The algorithm returns X_t after T iterations even if the validator has not accepted it; state explicitly whether this is the intended fallback and how the final answer is selected when the loop exits without acceptance.

Circularity Check

1 steps flagged · score 6.0 of 10

Label-dependent entity disambiguation in Appx. C.1.1 uses the ground-truth answer to select candidate entities, partially inflating the reported Hit@1 and the headline 51% relative gain.

  1. self definitional [Appendix C.1.1 (HYbGRAG Implementation, STARK)]
    "When extracting the entity name from the question, multiple entities in the knowledge base may have exactly the same name. In these cases, we select the entity that has the answer in its one-hop neighborhood for disambiguation, since it is not the focus of our paper. Moreover, these cases rarely happen, where only 3.83% and 0.07% of questions have this issue in STARK-MAG and STARK-PRIME, respectively."

    The task is to retrieve documents X ⊆ E satisfying the question, and Hit@1 measures whether the ground-truth answer entity/document is in the retrieved set. For the 3.83% of STARK-MAG questions with name collisions, the paper selects among same-name candidate entities the one whose one-hop neighborhood 'has the answer' — i.e., the label is used to choose the entity that the graph retriever will expand. This guarantees by construction that the answer appears in the retrieved neighborhood for those questions, so those Hit@1 successes are imposed rather than predicted. The reported average relative improvement of 51% (47.4% on MAG, 54.9% on PRIME) is therefore partly a label-contingent artifact.

full rationale

This is an empirical systems paper rather than a mathematical derivation, so the classic equation-level circularity is absent. The router and critic are evaluated end-to-end on held-out test sets, and few-shot examples are drawn from training/validation sets, which is standard practice. The STARK benchmark is co-authored by one of the present authors, but it is a public, externally used benchmark, so that self-citation is not load-bearing. The only concrete circular step is the entity-disambiguation rule in Appendix C.1.1: when multiple KG entities share the extracted name, the paper picks the entity whose one-hop neighborhood contains the ground-truth answer. Because the evaluation metric is Hit@1 on retrieved documents, this selection makes those test questions succeed by construction. The paper discloses the affected fractions (3.83% on MAG, 0.07% on PRIME), and the qualitative conclusion that HybGRAG beats AVATAR would likely survive a corrected evaluation, so the circularity is partial rather than total. Score 6 reflects that a non-negligible portion of the headline Hit@1 gain reduces to label-dependent construction.

Assumptions & free parameters 5 free parameters · 6 assumptions · 0 invented entities

The central claim rests on empirical assumptions about the LLM router and validator, the adequacy of the ego-graph and VSS rankers, and the validity of the STARK benchmark. No new theoretical entities are introduced, and no numeric parameters are fitted to test data; the listed free parameters are manually chosen hyperparameters that affect the result.

free parameters (5)
  • max_reflection_iterations_T = 4
    Set to four based on the ablation in Fig. 4 showing diminishing returns after two iterations; not derived from theory.
  • ego_graph_radius = 2
    The extracted ego-graph radius is capped at two hops; chosen to limit the search space while still capturing multi-hop relations.
  • commenter_icl_examples_stark = 30
    The commenter uses about 30 successful action-feedback pairs from the STARK training set for in-context learning; chosen as a small representative set.
  • commenter_icl_examples_crag = 5
    The CRAG commenter uses 5 action-feedback pairs from the validation set, as listed in the appendix.
  • crag_batch_size = 5
    A batch contains five web pages when the text retrieval module is used, as stated in Appendix C.1.1.
assumptions (6)
  • domain assumption The STARK benchmark provides a valid testbed for hybrid question answering, and its ground-truth document labels are correct.
    The method is evaluated entirely on STARK's test sets; if the benchmark labels are noisy or biased, the reported gains would be misleading. STARK is cited as Wu et al. 2024b, which includes a coauthor of this paper.
  • domain assumption An LLM router can extract the correct topic entities and useful relations from a hybrid question when given entity and relation types and few-shot examples.
    This is the foundation of the retriever bank. The paper shows refinement helps, but the first iteration must provide a starting point.
  • domain assumption The LLM validator can reliably judge whether a retrieved document satisfies the question given the document content and reasoning paths.
    The validator decides when to stop refinement. If it frequently accepts wrong documents or rejects correct ones, the method would not achieve the reported Hit@1.
  • domain assumption The ego-graph built from extracted entities and relations, intersected when multiple entities are used, contains the target documents.
    The hybrid retrieval module only returns entities within the ego-graph intersection; if the true answer lies outside, retrieval fails. The paper sets radius to 2 and assumes recall is sufficient.
  • domain assumption Vector similarity ranking over candidate documents is an effective ranker for hybrid questions.
    The final ranking within the hybrid module uses VSS, and the text module uses VSS exclusively. The choice of ada-002 or bge-m3 is not compared to other rankers.
  • domain assumption The ICL examples selected from the training set are representative of the test distribution and yield effective corrective feedback.
    The commenter relies on pre-collected successful experiences 'verified by ground truth' (Section 3.2). If these are cherry-picked or not representative, feedback quality drops.

how reviews work

0 comments
Cite this review

Pith. "Pith review of HybGRAG: Hybrid Retrieval-Augmented Generation on Textual and Relational Knowledge Bases." pith.science (2026). https://pith.science/paper/Q4TC5H6Y

@misc{pith2026241216311,
  author       = {Pith},
  title        = {Pith review of: HybGRAG: Hybrid Retrieval-Augmented Generation on Textual and Relational Knowledge Bases},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/Q4TC5H6Y}},
  note         = {Machine review of arXiv:2412.16311}
}
read the original abstract

Given a semi-structured knowledge base (SKB), where text documents are interconnected by relations, how can we effectively retrieve relevant information to answer user questions? Retrieval-Augmented Generation (RAG) retrieves documents to assist large language models (LLMs) in question answering; while Graph RAG (GRAG) uses structured knowledge bases as its knowledge source. However, many questions require both textual and relational information from SKB - referred to as "hybrid" questions - which complicates the retrieval process and underscores the need for a hybrid retrieval method that leverages both information. In this paper, through our empirical analysis, we identify key insights that show why existing methods may struggle with hybrid question answering (HQA) over SKB. Based on these insights, we propose HybGRAG for HQA consisting of a retriever bank and a critic module, with the following advantages: (1) Agentic, it automatically refines the output by incorporating feedback from the critic module, (2) Adaptive, it solves hybrid questions requiring both textual and relational information with the retriever bank, (3) Interpretable, it justifies decision making with intuitive refinement path, and (4) Effective, it surpasses all baselines on HQA benchmarks. In experiments on the STaRK benchmark, HybGRAG achieves significant performance gains, with an average relative improvement in Hit@1 of 51%.

Figures

Figures reproduced from arXiv: 2412.16311 by the authors.

Figure 1
Figure 1. HYBGRAG solves hybrid questions in SKB, which are semi-structured, involving textual and relational aspects. (a) RAG overlooks the interconnections between documents and does not meet the requirements specified by the relational aspect. (b) GRAG relies solely on the relational aspect and misidentifies the textual aspect as part of the relational one. (c) HYBGRAG refines the question routing through self-reflection a… view at source ↗
Figure 2
Figure 2. HYBGRAG wins in STARK, outperforming baselines by up to 21% in Hit@1. To solve HQA in SKB, we propose HYBGRAG. HYBGRAG handles hybrid questions with a re￾triever bank, which leverages both textual and re￾lational information simultaneously. To improve the accuracy of the retrieval, HYBGRAG performs self-reflection (Renze and Guven, 2024), which iter￾atively improves its question routing based on feed￾back from a car… view at source ↗
Figure 3
Figure 3. Design choices in HYBGRAG are necessary in STARK. We compare HYBGRAG with two variants: a validator without validation context, and a commenter with only 5-shot. Oracle uses ground truth during inference. 1 2 3 4 # of Iterations 0.50 0.55 0.60 0.65 Hit@1 0.26 0.28 STaRK-Prime STaRK-MAG [PITH_FULL_IMAGE:figures/full_fig_p006_3.png] view at source ↗
Figures from the paper (3 more)
Figure 4
Figure 4. Figure 4: HYBGRAG improves its question routing thanks to the critic module [PITH_FULL_IMAGE:figures/full_fig_p006_4.png]
Figure 5
Figure 5. Figure 5: HYBGRAG is interpretable. In examples from STARK-MAG, HYBGRAG successfully refines its entity and relation extraction based on corrective feedback from the critic module [PITH_FULL_IMAGE:figures/full_fig_p007_5.png]
Figure 6
Figure 6. Figure 6 [PITH_FULL_IMAGE:figures/full_fig_p012_6.png]

Discussion (0). Continue with ORCID to comment.

Forward citations

Cited by 2 Pith papers

Reviewed papers in the Pith corpus that reference this work. Sorted by Pith novelty score. Full citation record

  1. BYOKG-RAG: Multi-Strategy Graph Retrieval for Knowledge Graph Question Answering

    cs.CL 2025-07 reject novelty 6.0 of 10

    BYOKG-RAG combines LLM-generated entities, paths, queries, and candidate answers with multiple graph retrieval tools to answer questions over custom knowledge graphs without training data.

  2. HybridRAG-based LLM Agents for Low-Carbon Optimization in Low-Altitude Economy Networks

    cs.NI 2025-06 reject novelty 3.0 of 10

    HybridRAG merges keyword, vector, and graph retrieval to let an LLM formulate carbon-emission optimization problems for multi-UAV MEC networks, and R2DSAC solves them with a diffusion-regularized SAC plus neuron pruni...

Reference graph

Works this paper leans on

20 extracted references · 2 canonical work pages · cited by 2 Pith papers

  1. [4]

    Darren Edge, Ha Trinh, Newman Cheng, Joshua Bradley, Alex Chao, Apurva Mody, Steven Truitt, and Jonathan Larson

    Don’t forget to connect! improving rag with graph-based reranking.arXiv preprint arXiv:2405.18414. Darren Edge, Ha Trinh, Newman Cheng, Joshua Bradley, Alex Chao, Apurva Mody, Steven Truitt, and Jonathan Larson

  2. [5]

    arXiv preprint arXiv:2404.16130

    From local to global: A graph rag approach to query-focused summarization. arXiv preprint arXiv:2404.16130. Luyu Gao, Zhuyun Dai, Panupong Pasupat, Anthony Chen, Arun Tejasvi Chaganty, Yicheng Fan, Vin- cent Y Zhao, Ni Lao, Hongrae Lee, Da-Cheng Juan, et al

  3. [7]

    Yuntong Hu, Zhihan Lei, Zheng Zhang, Bo Pan, Chen Ling, and Liang Zhao

    G-retriever: Retrieval-augmented generation for textual graph understanding and ques- tion answering.arXiv preprint arXiv:2402.07630. Yuntong Hu, Zhihan Lei, Zheng Zhang, Bo Pan, Chen Ling, and Liang Zhao

  4. [8]

    Bowen Jin, Chulin Xie, Jiawei Zhang, Kashob Kumar Roy, Yu Zhang, Suhang Wang, Yu Meng, and Jiawei Han

    Grag: Graph retrieval-augmented generation.arXiv preprint arXiv:2405.16506. Bowen Jin, Chulin Xie, Jiawei Zhang, Kashob Kumar Roy, Yu Zhang, Suhang Wang, Yu Meng, and Jiawei Han

  5. [9]

    Jared Kaplan, Sam McCandlish, Tom Henighan, Tom B Brown, Benjamin Chess, Rewon Child, Scott Gray, Alec Radford, Jeffrey Wu, and Dario Amodei

    Graph chain-of-thought: Augmenting large language models by reasoning on graphs.arXiv preprint arXiv:2404.07103. Jared Kaplan, Sam McCandlish, Tom Henighan, Tom B Brown, Benjamin Chess, Rewon Child, Scott Gray, Alec Radford, Jeffrey Wu, and Dario Amodei

  6. [10]

    Vladimir Karpukhin, Barlas O˘guz, Sewon Min, Patrick Lewis, Ledell Wu, Sergey Edunov, Danqi Chen, and Wen-tau Yih

    Scaling laws for neural language models.arXiv preprint arXiv:2001.08361. Vladimir Karpukhin, Barlas O˘guz, Sewon Min, Patrick Lewis, Ledell Wu, Sergey Edunov, Danqi Chen, and Wen-tau Yih

  7. [11]

    Yunshi Lan, Gaole He, Jinhao Jiang, Jing Jiang, Wayne Xin Zhao, and Ji-Rong Wen

    Dense passage retrieval for open-domain question answering.arXiv preprint arXiv:2004.04906. Yunshi Lan, Gaole He, Jinhao Jiang, Jing Jiang, Wayne Xin Zhao, and Ji-Rong Wen

  8. [12]

    Shilong Li, Yancheng He, Hangyu Guo, Xingyuan Bu, Ge Bai, Jie Liu, Jiaheng Liu, Xingwei Qu, Yang- guang Li, Wanli Ouyang, et al

    Retrieval-augmented generation for knowledge-intensive nlp tasks.Advances in Neu- ral Information Processing Systems, 33:9459–9474. Shilong Li, Yancheng He, Hangyu Guo, Xingyuan Bu, Ge Bai, Jie Liu, Jiaheng Liu, Xingwei Qu, Yang- guang Li, Wanli Ouyang, et al. 2024a. Graphreader: Building graph-based agent to enhance long-context abilities of large langua...

Show all 20 references
  1. [13]

    Debjit Paul, Mete Ismayilzada, Maxime Peyrard, Beat- riz Borges, Antoine Bosselut, Robert West, and Boi Faltings

    Gnn- rag: Graph neural retrieval for large language model reasoning.arXiv preprint arXiv:2405.20139. Debjit Paul, Mete Ismayilzada, Maxime Peyrard, Beat- riz Borges, Antoine Bosselut, Robert West, and Boi Faltings

  2. [14]

    Shuofei Qiao, Ningyu Zhang, Runnan Fang, Yujie Luo, Wangchunshu Zhou, Yuchen Eleanor Jiang, Chengfei Lv, and Huajun Chen

    Graph retrieval-augmented generation: A survey.arXiv preprint arXiv:2408.08921. Shuofei Qiao, Ningyu Zhang, Runnan Fang, Yujie Luo, Wangchunshu Zhou, Yuchen Eleanor Jiang, Chengfei Lv, and Huajun Chen

  3. [15]

    Matthew Renze and Erhan Guven

    Autoact: Automatic agent learning from scratch via self-planning.arXiv preprint arXiv:2401.05268. Matthew Renze and Erhan Guven

  4. [16]

    Freda Shi, Xinyun Chen, Kanishka Misra, Nathan Scales, David Dohan, Ed H

    Self-reflection in llm agents: Effects on problem-solving perfor- mance.arXiv preprint arXiv:2405.06682. Freda Shi, Xinyun Chen, Kanishka Misra, Nathan Scales, David Dohan, Ed H. Chi, Nathanael Schärli, and Denny Zhou

  5. [17]

    Shirley Wu, Shiyu Zhao, Qian Huang, Kexin Huang, Michihiro Yasunaga, Kaidi Cao, Vassilis N Ioan- nidis, Karthik Subbian, Jure Leskovec, and James Zou

    Chain-of-thought prompting elicits rea- soning in large language models.Advances in neural information processing systems, 35:24824–24837. Shirley Wu, Shiyu Zhao, Qian Huang, Kexin Huang, Michihiro Yasunaga, Kaidi Cao, Vassilis N Ioan- nidis, Karthik Subbian, Jure Leskovec, an...

  6. [18]

    arXiv preprint arXiv:2401.15884

    Corrective retrieval augmented generation. arXiv preprint arXiv:2401.15884. Xiao Yang, Kai Sun, Hao Xin, Yushi Sun, Nikita Bhalla, Xiangsen Chen, Sajal Choudhary, Rongze Daniel Gui, Ziran Will Jiang, Ziyu Jiang, et al

  7. [19]

    Shunyu Yao, Jeffrey Zhao, Dian Yu, Nan Du, Izhak Shafran, Karthik R Narasimhan, and Yuan Cao

    Crag–comprehensive rag benchmark.arXiv preprint arXiv:2406.04744. Shunyu Yao, Jeffrey Zhao, Dian Yu, Nan Du, Izhak Shafran, Karthik R Narasimhan, and Yuan Cao

  8. [2006]

    In 2006 47th Annual IEEE Symposium on Foundations of Computer Science (FOCS’06), pages 475–486

    Lo- cal graph partitioning using pagerank vectors. In 2006 47th Annual IEEE Symposium on Foundations of Computer Science (FOCS’06), pages 475–486. IEEE. Akari Asai, Zeqiu Wu, Yizhong Wang, Avirup Sil, and Hannaneh Hajishirzi

  9. [2020]

    Jianlv Chen, Shitao Xiao, Peitian Zhang, Kun Luo, Defu Lian, and Zheng Liu

    Language models are few-shot learners.arXiv preprint arXiv:2005.14165. Jianlv Chen, Shitao Xiao, Peitian Zhang, Kun Luo, Defu Lian, and Zheng Liu

  10. [2021]

    pediatric liver cancer

    Qa-gnn: Rea- soning with language models and knowledge graphs for question answering. InNorth American Chap- ter of the Association for Computational Linguistics (NAACL). A Appendix: Benchmarks A.1 STARK We use two datasets from the STARK benchmark, STARK-MAG and STARK-PRIME. ...

  11. [2022]

    Zhibin Gou, Zhihong Shao, Yeyun Gong, yelong shen, Yujiu Yang, Nan Duan, and Weizhu Chen

    Rarr: Researching and revising what language models say, using language models.arXiv preprint arXiv:2210.08726. Zhibin Gou, Zhihong Shao, Yeyun Gong, yelong shen, Yujiu Yang, Nan Duan, and Weizhu Chen

  12. [2024]

    arXiv preprint arXiv:2402.03216

    Bge m3-embedding: Multi-lingual, multi-functionality, multi-granularity text embeddings through self-knowledge distillation. arXiv preprint arXiv:2402.03216. Jialin Dong, Bahare Fatemi, Bryan Perozzi, Lin F Yang, and Anton Tsitsulin

Pith tools

Reviewed August 11, 2026 · model on record in the stance chip above.