<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">LLMJudge: LLMs for Relevance Judgments</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Hossein</forename><forename type="middle">A</forename><surname>Rahmani</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">University College London</orgName>
								<address>
									<settlement>London</settlement>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Emine</forename><surname>Yilmaz</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">University College London</orgName>
								<address>
									<settlement>London</settlement>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Nick</forename><surname>Craswell</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">Microsoft</orgName>
								<address>
									<settlement>Seattle</settlement>
									<country>US</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Bhaskar</forename><surname>Mitra</surname></persName>
							<affiliation key="aff2">
								<orgName type="institution">Microsoft</orgName>
								<address>
									<settlement>Montréal</settlement>
									<country key="CA">Canada</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Paul</forename><surname>Thomas</surname></persName>
							<affiliation key="aff3">
								<orgName type="institution">Microsoft</orgName>
								<address>
									<settlement>Adelaide</settlement>
									<country key="AU">Australia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Charles</forename><forename type="middle">L A</forename><surname>Clarke</surname></persName>
							<affiliation key="aff4">
								<orgName type="institution">University of Waterloo</orgName>
								<address>
									<region>Ontario</region>
									<country key="CA">Canada</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Mohammad</forename><surname>Aliannejadi</surname></persName>
							<affiliation key="aff5">
								<orgName type="institution">University of Amsterdam</orgName>
								<address>
									<settlement>Amsterdam</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Clemencia</forename><surname>Siro</surname></persName>
							<affiliation key="aff5">
								<orgName type="institution">University of Amsterdam</orgName>
								<address>
									<settlement>Amsterdam</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Guglielmo</forename><surname>Faggioli</surname></persName>
							<affiliation key="aff6">
								<orgName type="institution">University of Padua</orgName>
								<address>
									<settlement>Padua</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff7">
								<orgName type="laboratory">The First Workshop on Large Language Models for Evaluation in Information Retrieval</orgName>
								<address>
									<addrLine>18 July 2024</addrLine>
									<settlement>Washington</settlement>
									<region>DC</region>
									<country key="US">United States</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">LLMJudge: LLMs for Relevance Judgments</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">670FCA9402145BB79713C437B0EDF9C5</idno>
					<idno type="DOI">10.1145/3626772.3657992</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T18:26+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract/>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>The LLMJudge challenge 1 is organized as part of the LLM4Eval 2 workshop <ref type="bibr" target="#b0">[1]</ref> at SIGIR 2024. Test collections are essential for evaluating information retrieval (IR) systems. The evaluation and tuning of a search system is largely based on relevance labels, which indicate whether a document is useful for a specific search and user. However, collecting relevance judgments on a large scale is costly and resource-intensive. Consequently, typical experiments rely on third-party labelers who may not always produce accurate annotations. The LLMJudge challenge aims to explore an alternative approach by using LLMs to generate relevance judgments. Recent studies have shown that LLMs can generate reliable relevance judgments for search systems. However, it remains unclear which LLMs can match the accuracy of human labelers, which prompts are most effective, how fine-tuned open-source LLMs compare to closed-source LLMs like GPT-4, whether there are biases in synthetically generated data, and if data leakage affects the quality of generated labels. This challenge will investigate these questions, and the collected data will be released as a package to support automatic relevance judgment research in information retrieval and search.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Related Work</head><p>Automatic relevance judgment has recently received significant attention in the Information Retrieval (IR) community. In earlier studies, Faggioli et al. <ref type="bibr" target="#b1">[2]</ref> studied different levels of human and LLMs collaboration for automatic relevance judgement. They suggested the need for humans to support and collaborate with LLMs for a human-machine collaboration judgment. Thomas et al. <ref type="bibr" target="#b2">[3]</ref> leverage LLMs capabilities in judgement at scale, in Microsoft Bing. They used real searcher feedback to consider an LLM and prompt in a way that matches the small sample of searcher preferences. Their experiments show that LLMs can be as good as human annotators in indicating the best systems. They also comprehensively investigated various prompts and prompt features for the task and revealed that LLM performance on judgments can varies with simple paraphrases of prompts. Recently, Rahmani et al. <ref type="bibr" target="#b3">[4]</ref> have studied fully synthetic test collection using LLMs. In their study, they not only generated synthetic queries but also synthetic judgment to build a full synthetic test collation for retrieval evaluation. They have shown that LLMs are able to generate a synthetic test collection that results in system ordering performance similar to evaluation results obtained using the real test collection. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">LLMJudge Task Design</head><p>The challenge will be, given the query and document as input, how they are relevant. Here, we use four-point scale judgments to evaluate the relevance of the query to document as follows:</p><p>• [3] Perfectly relevant: The passage is dedicated to the query and contains the exact answer.</p><p>• [2] Highly relevant: The passage has some answers for the query, but the answer may be a bit unclear, or hidden amongst extraneous information. • [1] Related: The passage seems related to the query but does not answer it.</p><p>• [0] Irrelevant: The passage has nothing to do with the query.</p><p>The task is, by providing the datasets that include queries, documents, and query-document files to participants, to ask LLMs to generate a score [0, 1, 2, 3] indicating the relevance of the query to the document.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">LLMJudge Data</head><p>The LLMJudge challenge dataset is built upon the passage retrieval task dataset of the TREC 2023 Deep Learning track 3 (TREC-DL 2023) <ref type="bibr" target="#b4">[5]</ref>. Table <ref type="table" target="#tab_0">1</ref> shows the statistics of the LLMJudge challenge datasets. We divide the data into development and test sets. The test set is used for the generation of judgment by participants, while the development set could be used for few-shot or fine-tuning purposes. The datasets, sample prompt, and the quick starter for automatic judgment can be found at the following repository: https://github.com/llm4eval/LLMJudge</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Evaluation</head><p>Participants' results will then be evaluated in two methods after submission:</p><p>• automated evaluation metrics on human labels in the test set hidden from the participants; • system ordering evaluation of multiple search systems on human judgments and LLM-based judgments</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Submissions and Results</head><p>In order to evaluate the quality of the generated labels, we used Cohen's 𝜅 to see the labeler's agreement with LLMJudge test data at query-document level and the Kendall's 𝜅 to check the labeler's agreement with LLMJudge test data on system ordering, i.e., the runs that submitted to TREC DL 2023. In total, we had 39 submissions (i.e., the 39 labelers) from 7 groups from National Institute of Standards and  Figure <ref type="figure" target="#fig_0">1</ref> shows the performance of submitted labelers on the LLMJudge test set. The x-axis represents Cohen's 𝜅, and the y-axis shows the labelers' agreement on system ordering. Labelers exhibit low variability in Kendall's 𝜏 but greater variability in Cohen's 𝜅. Most labelers cluster within a narrow range of 𝜏 values, indicating consistent system rankings but more variation in inter-rater reliability, as measured by Cohen's 𝜅. This suggests that while labelers generally agree on rankings, their exact labels are less consistent, leading to the observed variability in 𝜅.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Scatter plot of Cohen's 𝜅 and Kendall's 𝜏 for submitted labelers</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1</head><label>1</label><figDesc>Statistics of LLMJudge Dataset</figDesc><table><row><cell></cell><cell cols="2">Dev Test</cell></row><row><cell># queries</cell><cell>25</cell><cell>25</cell></row><row><cell># passage</cell><cell cols="2">7,224 4,414</cell></row><row><cell># qrels</cell><cell cols="2">7,263 4,423</cell></row><row><cell># irrelevant (0)</cell><cell cols="2">4,538 2,005</cell></row><row><cell># related (1)</cell><cell cols="2">1,403 1,233</cell></row><row><cell># highly relevant (2)</cell><cell>625</cell><cell>808</cell></row><row><cell># perfectly relevant (3)</cell><cell>697</cell><cell>377</cell></row></table></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgment</head><p>The challenge is organized as a joint effort by the University College London, Microsoft, the University of Amsterdam, the University of Waterloo, and the University of Padua. The views expressed in the content are solely those of the authors and do not necessarily reflect the views or endorsements of their employers and/or sponsors. This work is supported by the Engineering and Physical Sciences Research Council [EP/S021566/1], the EPSRC Fellowship titled "Task Based Information Retrieval" [EP/P024289/1], CAMEO, PRIN 2022 n. 2022ZLL7MW.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Llm4eval: Large language model for evaluation in ir</title>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">A</forename><surname>Rahmani</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Siro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Aliannejadi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Craswell</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">L A</forename><surname>Clarke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Faggioli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Mitra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Thomas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Yilmaz</surname></persName>
		</author>
		<idno type="DOI">10.1145/3626772.3657992</idno>
		<idno>doi:10.1145/3626772.3657992</idno>
		<ptr target="https://doi.org/10.1145/3626772.3657992" />
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 47th International ACM SIGIR Conference on Research and Development in Information Retrieval, SIGIR &apos;24</title>
				<meeting>the 47th International ACM SIGIR Conference on Research and Development in Information Retrieval, SIGIR &apos;24<address><addrLine>New York, NY, USA</addrLine></address></meeting>
		<imprint>
			<publisher>Association for Computing Machinery</publisher>
			<date type="published" when="2024">2024</date>
			<biblScope unit="page" from="3040" to="3043" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Perspectives on large language models for relevance judgment</title>
		<author>
			<persName><forename type="first">G</forename><surname>Faggioli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Dietz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">L</forename><surname>Clarke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Demartini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Hagen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Hauff</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Kando</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Kanoulas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Potthast</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Stein</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 2023 ACM SIGIR International Conference on Theory of Information Retrieval</title>
				<meeting>the 2023 ACM SIGIR International Conference on Theory of Information Retrieval</meeting>
		<imprint>
			<date type="published" when="2023">2023</date>
			<biblScope unit="page" from="39" to="50" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<author>
			<persName><forename type="first">P</forename><surname>Thomas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Spielman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Craswell</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Mitra</surname></persName>
		</author>
		<idno type="arXiv">arXiv:2309.10621</idno>
		<title level="m">Large language models can accurately predict searcher preferences</title>
				<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
	<note type="report_type">arXiv preprint</note>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">A</forename><surname>Rahmani</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Craswell</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Yilmaz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Mitra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Campos</surname></persName>
		</author>
		<idno type="arXiv">arXiv:2405.07767</idno>
		<title level="m">Synthetic test collections for retrieval evaluation</title>
				<imprint>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
	<note type="report_type">arXiv preprint</note>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Overview of the trec 2023 deep learning track</title>
		<author>
			<persName><forename type="first">N</forename><surname>Craswell</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Mitra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Yilmaz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">A</forename><surname>Rahmani</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Campos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Lin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">M</forename><surname>Voorhees</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Soboroff</surname></persName>
		</author>
		<ptr target="https://www.microsoft.com/en-us/research/publication/overview-of-the-trec-2023-deep-learning-track/" />
	</analytic>
	<monogr>
		<title level="m">Text REtrieval Conference (TREC), NIST, TREC</title>
				<imprint>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
