Datasets:
docs: revert body --- back to em-dash
Browse files
README.md
CHANGED
|
@@ -97,7 +97,7 @@ configs:
|
|
| 97 |
<!-- Provide a quick summary of the dataset. -->
|
| 98 |
|
| 99 |
ReCaRe (pronounced "re-care") is a bilingual legal benchmark for **Revision
|
| 100 |
-
Candidate Retrieval (RCR)**
|
| 101 |
that constitute plausible candidates for an authoritative revision. It
|
| 102 |
spans European Union law (EUR-Lex, English) and Japanese law (e-Gov,
|
| 103 |
Japanese), with 703 amendment events and ~181k articles, supporting two
|
|
@@ -113,8 +113,8 @@ Document corpora in regulated domains evolve: statutes are amended, internal
|
|
| 113 |
policies revised, software specifications updated. Yet most information
|
| 114 |
retrieval research has framed retrieval as a one-shot question-answering
|
| 115 |
problem over a frozen corpus, leaving the IR aspects of *document
|
| 116 |
-
maintenance*
|
| 117 |
-
documents must change with them
|
| 118 |
|
| 119 |
ReCaRe formalizes two complementary RCR tasks over bilingual corpora of EU and Japanese law:
|
| 120 |
|
|
@@ -159,7 +159,7 @@ ReCaRe is **not** designed for, and should not be used as, a basis for:
|
|
| 159 |
production legal workflow without expert review. Retrieved articles are
|
| 160 |
*candidates* for expert review, not authoritative outputs.
|
| 161 |
- Provision of legal advice to end-users.
|
| 162 |
-
- Inference of personal or demographic information about individuals
|
| 163 |
data contains only public legal text, but personal names appearing in
|
| 164 |
legal records (e.g. drafters, ministers) should not be used to build
|
| 165 |
profiles of those individuals.
|
|
@@ -205,7 +205,7 @@ amending act. The metadata configs are provided for downstream provenance
|
|
| 205 |
analyses and are not required to run the retrieval tasks themselves.
|
| 206 |
|
| 207 |
**Splits.** The `qrels-*` configs use train / validation / test splits. The
|
| 208 |
-
`corpus-*`, `queries-*`, and `metadata-*` configs are not split
|
| 209 |
corpus is used at retrieval time, and queries split membership is encoded
|
| 210 |
through the qrels.
|
| 211 |
|
|
@@ -227,7 +227,7 @@ qrels = load_dataset("kasys/ReCaRe", "qrels-rat2rev-en") # train/validation/t
|
|
| 227 |
|
| 228 |
Existing legal-IR benchmarks (e.g. COLIEE, BSARD, LeCaRD, STARD,
|
| 229 |
LegalBench-RAG) cover statutory or case-law question answering but not
|
| 230 |
-
*document maintenance*
|
| 231 |
corpus evolves. ReCaRe was constructed to give the IR community a shared,
|
| 232 |
bilingual benchmark for two practically motivated retrieval tasks
|
| 233 |
(Rat2Rev, Rev2Rev) over legal corpora, in two jurisdictions whose
|
|
|
|
| 97 |
<!-- Provide a quick summary of the dataset. -->
|
| 98 |
|
| 99 |
ReCaRe (pronounced "re-care") is a bilingual legal benchmark for **Revision
|
| 100 |
+
Candidate Retrieval (RCR)** — locating the provisions of a legal corpus
|
| 101 |
that constitute plausible candidates for an authoritative revision. It
|
| 102 |
spans European Union law (EUR-Lex, English) and Japanese law (e-Gov,
|
| 103 |
Japanese), with 703 amendment events and ~181k articles, supporting two
|
|
|
|
| 113 |
policies revised, software specifications updated. Yet most information
|
| 114 |
retrieval research has framed retrieval as a one-shot question-answering
|
| 115 |
problem over a frozen corpus, leaving the IR aspects of *document
|
| 116 |
+
maintenance* — finding which documents need to change, and which other
|
| 117 |
+
documents must change with them — comparatively underexplored.
|
| 118 |
|
| 119 |
ReCaRe formalizes two complementary RCR tasks over bilingual corpora of EU and Japanese law:
|
| 120 |
|
|
|
|
| 159 |
production legal workflow without expert review. Retrieved articles are
|
| 160 |
*candidates* for expert review, not authoritative outputs.
|
| 161 |
- Provision of legal advice to end-users.
|
| 162 |
+
- Inference of personal or demographic information about individuals — the
|
| 163 |
data contains only public legal text, but personal names appearing in
|
| 164 |
legal records (e.g. drafters, ministers) should not be used to build
|
| 165 |
profiles of those individuals.
|
|
|
|
| 205 |
analyses and are not required to run the retrieval tasks themselves.
|
| 206 |
|
| 207 |
**Splits.** The `qrels-*` configs use train / validation / test splits. The
|
| 208 |
+
`corpus-*`, `queries-*`, and `metadata-*` configs are not split — the full
|
| 209 |
corpus is used at retrieval time, and queries split membership is encoded
|
| 210 |
through the qrels.
|
| 211 |
|
|
|
|
| 227 |
|
| 228 |
Existing legal-IR benchmarks (e.g. COLIEE, BSARD, LeCaRD, STARD,
|
| 229 |
LegalBench-RAG) cover statutory or case-law question answering but not
|
| 230 |
+
*document maintenance* — finding which provisions must change when a
|
| 231 |
corpus evolves. ReCaRe was constructed to give the IR community a shared,
|
| 232 |
bilingual benchmark for two practically motivated retrieval tasks
|
| 233 |
(Rat2Rev, Rev2Rev) over legal corpora, in two jurisdictions whose
|