Update README

README.md

@@ -22,11 +22,12 @@ pretty_name: OracleProto Forecasting Eval Set
 
 # OracleProto: Forecasting Evaluation Set
 
-**Dataset:** [`MaYiding/OracleProto`](https://huggingface.co/datasets/MaYiding/OracleProto) ·
-**Framework:** [`MaYiding/OracleProto`](https://github.com/MaYiding/OracleProto) ·
+**Dataset:** [`Hugging Face`](https://huggingface.co/datasets/MaYiding/OracleProto)
+**GitHub Repo:** [`Github`](https://github.com/MaYiding/OracleProto)
+**Chinese Doc:** [[`中文文档`](https://huggingface.co/datasets/MaYiding/OracleProto/blob/main/README-ZH.md)]
 **License:** MIT
 
-A SQLite-packaged evaluation set of 80 hand-curated forecasting questions on real-world events, with resolution dates between 2026-03-12 and 2026-04-14, released alongside the [OracleProto framework](https://github.com/MaYiding/OracleProto). Both the rows and the byte-stable prompt-reconstruction recipe ship inside a single file, `forecast_eval_set_example.db`, which holds two tables: `forecast_eval_set_example` (the 80 rows) and `dataset_metadata` (the recipe).
+A SQLite-packaged evaluation set of 80 hand-curated forecasting questions on real-world events, with resolution dates between 2026-03-12 and 2026-04-14, released alongside the [GitHub Repo](https://github.com/MaYiding/OracleProto). Both the rows and the byte-stable prompt-reconstruction recipe ship inside a single file, `forecast_eval_set_example.db`, which holds two tables: `forecast_eval_set_example` (the 80 rows) and `dataset_metadata` (the recipe).
 
 ---
 
@@ -34,11 +35,10 @@ A SQLite-packaged evaluation set of 80 hand-curated forecasting questions on rea
 
 | Field                  | Value                                                                  |
 | ---------------------- | ---------------------------------------------------------------------- |
-| Schema version         | `v1.0`                                                                 |
 | Release date           | `2026-04-29`                                                           |
 | Rows                   | 80                                                                     |
 | Splits                 | `train` (80); single split, intended as a held-out evaluation set      |
-| Resolution-date range  | `2026-03-12` → `2026-04-14` (GMT+8)                                    |
+| Resolution-date range  | `2026-03-12` → `2026-04-14`                                            |
 | Question types         | `yes_no`, `binary_named`, `multiple_choice`                            |
 | Choice types           | `single` (one correct letter), `multi` (one-or-more correct letters)   |
 | Database file          | `forecast_eval_set_example.db` (SQLite 3, ~52 KB)                      |
@@ -48,12 +48,12 @@ A SQLite-packaged evaluation set of 80 hand-curated forecasting questions on rea
 
 ### Type distribution
 
-| `question_type`     | `choice_type` | Rows |
-| ------------------- | ------------- | ---- |
-| `yes_no`            | `single`      | 37   |
-| `binary_named`      | `single`      | 3    |
-| `multiple_choice`   | `single`      | 32   |
-| `multiple_choice`   | `multi`       | 8    |
+| `question_type`     | `choice_type` | Rows   |
+| ------------------- | ------------- | ------ |
+| `yes_no`            | `single`      | 37     |
+| `binary_named`      | `single`      | 3      |
+| `multiple_choice`   | `single`      | 32     |
+| `multiple_choice`   | `multi`       | 8      |
 | **Total**           |               | **80** |
 
 `yes_no` is binary Yes/No; `binary_named` is binary between two named entities such as sports teams, fighters, or sides; `multiple_choice` carries at least three labelled options with one or more correct letters allowed, and "None of the above" is a valid answer when listed. Each row stores the exact option labels; letter `A` maps to `options[0]`, `B` to `options[1]`, and so on (§3.4 covers labels beyond `Z`).
@@ -430,25 +430,17 @@ Without the OracleProto harness in place, treat the resulting numbers as upper b
 
 ---
 
-## 10. Versioning
-
-* **`v1.0` (2026-04-29).** Initial public example release. 80 rows; resolution dates 2026-03-12 → 2026-04-14; pipeline passes 1–5 above; 0 critical / 0 high / 0 medium ambiguity issues remaining.
-
-The schema version is recorded inside the database at `dataset_metadata.features_json.schema_version`, so consumers can pin against it without re-deriving from the file's hash.
-
----
-
-## 11. License
+## 10. License
 
 Released under the **MIT License** (see `LICENSE`). The upstream questions originate from a public HuggingFace forecasting set; the curation work, schema, prompt-reconstruction recipe, and answer encodings in this release are the contribution of this project.
 
 ---
 
-## 12. Contact and contributions
+## 11. Contact and contributions
 
 Issues, schema feedback, and ambiguity reports are welcome. If a row's ground truth has changed, or its framing is ambiguous under §5.5, open an issue in the relevant repository:
 
-* Dataset (this repo): [`MaYiding/OracleProto` on Hugging Face](https://huggingface.co/datasets/MaYiding/OracleProto/discussions) for row-level questions, ambiguity reports, and label disputes.
-* Framework code: [`MaYiding/OracleProto` on GitHub](https://github.com/MaYiding/OracleProto/issues) for evaluator, parser, or harness behaviour.
+* Dataset: [`MaYiding/OracleProto` on Hugging Face](https://huggingface.co/datasets/MaYiding/OracleProto/discussions) for row-level questions, ambiguity reports, and label disputes.
+* Code Repo: [`MaYiding/OracleProto` on GitHub](https://github.com/MaYiding/OracleProto/issues) for evaluator, parser, or harness behaviour.
 
 Row-level reports should include the `id`, the disputed framing, and where available a primary source; those are the inputs the curation pipeline needs to update the row in the next release.