Create README.md
#16
by LiamDuero - opened
README.md
ADDED
|
@@ -0,0 +1,198 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
license: apache-2.0
|
| 3 |
+
language:
|
| 4 |
+
- en
|
| 5 |
+
pretty_name: Telco-Retrieve QnA (3GPP)
|
| 6 |
+
task_categories:
|
| 7 |
+
- question-answering
|
| 8 |
+
- multiple-choice
|
| 9 |
+
- text-generation
|
| 10 |
+
tags:
|
| 11 |
+
- telecom
|
| 12 |
+
- telecommunications
|
| 13 |
+
- 3gpp
|
| 14 |
+
- rag
|
| 15 |
+
- retrieval-augmented-generation
|
| 16 |
+
- evaluation
|
| 17 |
+
- benchmark
|
| 18 |
+
- synthetic
|
| 19 |
+
- ground-truth
|
| 20 |
+
configs:
|
| 21 |
+
- config_name: question_pool
|
| 22 |
+
data_files: question_pool_3gpp.json
|
| 23 |
+
- config_name: set_840
|
| 24 |
+
data_files: 3gpp_question_set_840.json
|
| 25 |
+
- config_name: set_105
|
| 26 |
+
data_files: 3gpp_question_set_105.json
|
| 27 |
+
- config_name: set_84
|
| 28 |
+
data_files: 3gpp_question_set_84.json
|
| 29 |
+
# NOTE: records live under the "questions" key of each JSON object. If the dataset
|
| 30 |
+
# viewer should expand them, either add a loading script or flatten to JSONL.
|
| 31 |
+
---
|
| 32 |
+
|
| 33 |
+
# Telco-Retrieve QnA (3GPP)
|
| 34 |
+
|
| 35 |
+
Synthetic, expert-validated question–answer pairs over **3GPP** standards, built to evaluate
|
| 36 |
+
retrieval-augmented generation (RAG) and closed-book LLM performance on telecom domain knowledge.
|
| 37 |
+
Part of the **[GSMA Open Telco AI](https://www.open-telco.ai/)** initiative and the companion
|
| 38 |
+
evaluation set for [`GSMA/telco-retrieve-chunks`](https://huggingface.co/datasets/GSMA/telco-retrieve-chunks)
|
| 39 |
+
and the [`open-telco-rag`](https://github.com/Znbne/telco-retrieve) pipeline.
|
| 40 |
+
|
| 41 |
+
Every question is grounded in a specific chunk of a real 3GPP document, carries a canonical spec
|
| 42 |
+
citation, and has passed a multi-stage LLM jury followed by human review.
|
| 43 |
+
|
| 44 |
+
## Dataset Summary
|
| 45 |
+
|
| 46 |
+
A validated pool of **1,227** 3GPP questions plus three pre-drawn, stratified evaluation splits of
|
| 47 |
+
different sizes. Questions come in three formats — multiple-choice (`mc`, 2–5 options), true/false
|
| 48 |
+
(`tf`), and open-ended (`open`) — and are filtered so that every retained question is answerable
|
| 49 |
+
*from its source chunk*, discriminative against similar chunks, and non-trivial without retrieval.
|
| 50 |
+
|
| 51 |
+
Intended as a **held-out benchmark, not training data**.
|
| 52 |
+
|
| 53 |
+
- **Corpus:** 3GPP — Release 8 through Release 19, all series (TS 23/28/32/33/38 …)
|
| 54 |
+
- **Source chunks:** [`GSMA/telco-retrieve-chunks`](https://huggingface.co/datasets/GSMA/telco-retrieve-chunks) (`3gpp` export)
|
| 55 |
+
- **Generation:** [`telco-qna-generation`](https://github.com/Znbne/telco-qna-generation) declarative Flows
|
| 56 |
+
- **All records:** `validated: true` (expert-reviewed)
|
| 57 |
+
|
| 58 |
+
## Files
|
| 59 |
+
|
| 60 |
+
| File | Config | Questions | MC / TF / OE | Size | What it is |
|
| 61 |
+
|---|---|---:|---|---:|---|
|
| 62 |
+
| `question_pool_3gpp.json` | `question_pool` | 1,227 | 475 / 514 / 238 | 3.6 MB | The full validated question pool. Draw your own samples from this. |
|
| 63 |
+
| `3gpp_question_set_840.json` | `set_840` | 840 | 400 / 400 / 40 | 2.4 MB | Large stratified evaluation sample (difficulty-first + 3GPP-series-stratified). |
|
| 64 |
+
| `3gpp_question_set_105.json` | `set_105` | 105 | 55 / 40 / 10 | 317 KB | Small stratified sample; highest-difficulty preferred, series-stratified. |
|
| 65 |
+
| `3gpp_question_set_84.json` | `set_84` | 84 | 40 / 40 / 4 | 254 KB | Independent 84-question draw (40/40/4), same stratification. |
|
| 66 |
+
|
| 67 |
+
The three `*_question_set_*` files are **subsets drawn from `question_pool_3gpp.json`** — they
|
| 68 |
+
overlap with the pool and, partially, with each other. Pick one split as your benchmark; don't sum
|
| 69 |
+
row counts across files.
|
| 70 |
+
|
| 71 |
+
> `question_pool_3gpp.json`'s top-level `_generated` header still reads "Requires expert validation
|
| 72 |
+
> before use as ground truth" — that string is a stale default. Every record in it has
|
| 73 |
+
> `validated: true`; trust the per-record field, not the file header.
|
| 74 |
+
|
| 75 |
+
## Dataset Structure
|
| 76 |
+
|
| 77 |
+
Each file is a single JSON object:
|
| 78 |
+
|
| 79 |
+
```json
|
| 80 |
+
{
|
| 81 |
+
"_corpus": "3gpp",
|
| 82 |
+
"_description": "…how this split was drawn…",
|
| 83 |
+
"_generated": "2026-08-27T20:08:55Z",
|
| 84 |
+
"questions": [ { …record… }, … ]
|
| 85 |
+
}
|
| 86 |
+
```
|
| 87 |
+
|
| 88 |
+
### Record fields
|
| 89 |
+
|
| 90 |
+
| Field | Type | Notes |
|
| 91 |
+
|---|---|---|
|
| 92 |
+
| `question_id` | string | 12-hex stable id (join key for review sheets) |
|
| 93 |
+
| `question` | string | Question text |
|
| 94 |
+
| `reference_answer` | string | Gold answer. `mc`: the correct option; `tf`: `"true"`/`"false"`; `open`: short free-text answer |
|
| 95 |
+
| `answer_type` | string | `mc` \| `tf` \| `open` |
|
| 96 |
+
| `options` | object | **MC only** — map of option label → option text |
|
| 97 |
+
| `explanation` | string | **TF only** — why the statement is true/false |
|
| 98 |
+
| `difficulty` | string | Model-assigned at generation (`unspecified` if not set) |
|
| 99 |
+
| `keywords` | list[string] | Salient terms, for keyword-overlap retrieval metrics |
|
| 100 |
+
| `corpus` | string | Always `3gpp` in this dataset |
|
| 101 |
+
| `canonical_source` | string | Human-readable citation, e.g. `TS 28.312 (Rel-18)` |
|
| 102 |
+
| `release` | string | 3GPP release the source chunk was ingested from (`""` where N/A) |
|
| 103 |
+
| `spec_version` | string | Full spec version string (present in some sets) |
|
| 104 |
+
| `chunk_id` | string | Exact source chunk in `GSMA/telco-retrieve-chunks` |
|
| 105 |
+
| `source_document` | string | Source file the chunk came from |
|
| 106 |
+
| `source_text` | string | **Verbatim excerpt** of the 3GPP chunk the question was written from |
|
| 107 |
+
| `generated` | bool | Always `true` (all items model-generated) |
|
| 108 |
+
| `validated` | bool | `true` — expert-reviewed and merged into the canonical set |
|
| 109 |
+
| `validation_passed` | bool | Answerability / self-consistency check |
|
| 110 |
+
| `validation_note` | string | Note from the answerability check |
|
| 111 |
+
| `domain_relevance_passed` | bool | LLM jury: is this a telecom-domain question |
|
| 112 |
+
| `faithfulness_passed` | bool | LLM jury: answer entailed by `source_text` |
|
| 113 |
+
| `semantic_correctness_passed` | bool | LLM jury: answer is semantically correct |
|
| 114 |
+
| `relevance_passed` | bool | LLM jury: question relevant to the chunk |
|
| 115 |
+
| `competitor_chunks` | int | # distractor chunks in the discriminativeness check |
|
| 116 |
+
| `competitor_correct_ratio` | float | Fraction of distractor chunks that also "answer" the question (lower = more discriminative) |
|
| 117 |
+
| `competitor_threshold_used` | float | Pass threshold applied to `competitor_correct_ratio` |
|
| 118 |
+
| `jury_no_context_score` | float | Empirical-difficulty jury score with **no** retrieved context |
|
| 119 |
+
| `jury_with_context_score` | float | Empirical-difficulty jury score **with** context |
|
| 120 |
+
| `no_context_threshold_used` | float | Threshold separating too-easy from rag-suitable |
|
| 121 |
+
| `empirical_difficulty` | string | e.g. `rag_suitable`, `too_easy`, `unanswerable` |
|
| 122 |
+
| `review_status` | string | Human review outcome |
|
| 123 |
+
| `reviewer` | string | Reviewer id |
|
| 124 |
+
| `review_notes` | string | Human reviewer notes |
|
| 125 |
+
|
| 126 |
+
## Supported Tasks
|
| 127 |
+
|
| 128 |
+
- **RAG evaluation** — retrieve over `GSMA/telco-retrieve-chunks` (`3gpp`), answer, score against
|
| 129 |
+
`reference_answer` / `options`, and check retrieval with `canonical_source` (canonical hit rate).
|
| 130 |
+
- **Closed-book QA** — no-retrieval baseline: parametric 3GPP knowledge and abstention behaviour.
|
| 131 |
+
- **Multiple-choice accuracy** and **open-ended answer correctness** (LLM-graded vs `reference_answer`).
|
| 132 |
+
|
| 133 |
+
The `open-telco-rag evaluate` harness consumes a split directly as
|
| 134 |
+
`configs/eval_questions/3gpp.json`.
|
| 135 |
+
|
| 136 |
+
## Source Data & Curation
|
| 137 |
+
|
| 138 |
+
### Source
|
| 139 |
+
|
| 140 |
+
3GPP specifications (Rel-8 → Rel-19, all series), ingested and chunked in
|
| 141 |
+
`GSMA/telco-retrieve-chunks`. Underlying 3GPP text was sourced via the TSpec-LLM corpus and the
|
| 142 |
+
3GPP spec archive (`3gpp.org/ftp/Specs/archive`).
|
| 143 |
+
|
| 144 |
+
### Generation pipeline
|
| 145 |
+
|
| 146 |
+
Produced by [`telco-qna-generation`](https://github.com/Znbne/telco-qna-generation) —
|
| 147 |
+
declarative YAML **Flows** chaining composable blocks:
|
| 148 |
+
|
| 149 |
+
1. **Sample chunks** — stratified over the corpus by 3GPP TS series.
|
| 150 |
+
2. **Generate questions** — per-format prompts with 3GPP-specific guidance, written from the source
|
| 151 |
+
text (not a summary).
|
| 152 |
+
3. **Validate & dedup** — answerability check; prefix-dedup against prior drafts.
|
| 153 |
+
4. **LLM jury** — grounding, answerability, faithfulness, domain-relevance, semantic-correctness and
|
| 154 |
+
relevance blocks; each records a `*_passed` flag.
|
| 155 |
+
5. **Competitor filter** — re-asks the question against distractor chunks; keeps only questions a
|
| 156 |
+
reader can't answer from the wrong chunk.
|
| 157 |
+
6. **Empirical-difficulty jury** — scores the question with and without context; drops `too_easy`
|
| 158 |
+
and `unanswerable`, keeps `rag_suitable`.
|
| 159 |
+
7. **Draft → human review → merge** — output is a *draft* (`generated: true, validated: false`)
|
| 160 |
+
until a domain expert reviews it and it is explicitly merged into the canonical set
|
| 161 |
+
(`validated: true`).
|
| 162 |
+
|
| 163 |
+
### Evaluation splits
|
| 164 |
+
|
| 165 |
+
`question_pool_3gpp.json` is the merged, validated pool. The `*_question_set_*` files are drawn
|
| 166 |
+
from it **difficulty-first** (highest-difficulty questions preferred) and **stratified by 3GPP
|
| 167 |
+
series** (from the `chunk_id` prefix) to preserve topical spread. `set_105` and `set_84` are
|
| 168 |
+
independent draws; `set_84` is the 40/40/4 subset used for the thesis's per-question analysis.
|
| 169 |
+
|
| 170 |
+
### Curation rationale
|
| 171 |
+
|
| 172 |
+
The aim is a benchmark that isolates *retrieval-conditioned* 3GPP knowledge: questions must be
|
| 173 |
+
answerable from a single cited chunk, hard to answer without it, and discriminative against similar
|
| 174 |
+
chunks — so RAG lift over a closed-book baseline is measurable rather than confounded by questions
|
| 175 |
+
a model already knows or cannot answer at all.
|
| 176 |
+
|
| 177 |
+
## Considerations & Limitations
|
| 178 |
+
|
| 179 |
+
- **Synthetic questions, LLM-assisted validation.** Every question is model-generated and most
|
| 180 |
+
filters are LLM juries. Human review is a final gate but is single/limited-reviewer, so residual
|
| 181 |
+
errors in `reference_answer` or `canonical_source` are possible. `validated: true` means
|
| 182 |
+
"expert-checked", not "formally adjudicated".
|
| 183 |
+
- **Single corpus.** 3GPP only. Not representative of O-RAN, ETSI, ITU-T, CAMARA, GSMA or TM Forum,
|
| 184 |
+
which the `telco-qna-generation` toolkit can target but this dataset does not cover.
|
| 185 |
+
- **Point-in-time.** Tied to specific spec releases (`release` / `canonical_source`); 3GPP moves on.
|
| 186 |
+
- **Not training data.** Held-out evaluation only. Do not fine-tune on it or leak it into training.
|
| 187 |
+
- **Grader dependence.** OE scoring uses an LLM grader against `reference_answer`; absolute OE
|
| 188 |
+
numbers depend on that grader.
|
| 189 |
+
- **English only.**
|
| 190 |
+
|
| 191 |
+
## Licensing
|
| 192 |
+
|
| 193 |
+
- **QnA annotations** (questions, answers, keywords, judge/review metadata): **Apache-2.0**,
|
| 194 |
+
consistent with the `telco-qna-generation` toolkit. *(Set here as `apache-2.0`; change if GSMA
|
| 195 |
+
requires a different licence for this repo.)*
|
| 196 |
+
- **`source_text`** contains short verbatim excerpts of 3GPP specifications. Those excerpts remain
|
| 197 |
+
subject to 3GPP's copyright and redistribution terms and those of the upstream source
|
| 198 |
+
(the TSpec-LLM dataset / the 3GPP spec archive). Downstream users are responsible for compliance.
|