Remove labeled prediction examples
Browse files
README.md
CHANGED
|
@@ -99,7 +99,7 @@ deterministically at import time.
|
|
| 99 |
Recommended public prediction format:
|
| 100 |
|
| 101 |
```json
|
| 102 |
-
{"task_id": "
|
| 103 |
```
|
| 104 |
|
| 105 |
`RUN.md` has a fuller harness contract, adapter skeleton, prompt template, and a
|
|
|
|
| 99 |
Recommended public prediction format:
|
| 100 |
|
| 101 |
```json
|
| 102 |
+
{"task_id": "example_task_id", "answer": "<model-output>", "model": "your-model-name"}
|
| 103 |
```
|
| 104 |
|
| 105 |
`RUN.md` has a fuller harness contract, adapter skeleton, prompt template, and a
|
RUN.md
CHANGED
|
@@ -36,7 +36,7 @@ The public split has no labels, so this produces predictions for inspection or
|
|
| 36 |
private scoring. A useful prediction file format is JSONL:
|
| 37 |
|
| 38 |
```json
|
| 39 |
-
{"task_id": "
|
| 40 |
```
|
| 41 |
|
| 42 |
Minimal adapter skeleton:
|
|
|
|
| 36 |
private scoring. A useful prediction file format is JSONL:
|
| 37 |
|
| 38 |
```json
|
| 39 |
+
{"task_id": "example_task_id", "answer": "<model-output>", "model": "your-model-name"}
|
| 40 |
```
|
| 41 |
|
| 42 |
Minimal adapter skeleton:
|