File size: 3,829 Bytes
b5137f6 5b47d38 a8e7c28 5b47d38 a8e7c28 5b47d38 a8e7c28 5b47d38 a8e7c28 5b47d38 a8e7c28 5b47d38 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 | ---
license: cc
---
# ALWM Data
Data used by ALWM.
## Dataset statistics
<table>
<thead>
<tr>
<th rowspan="2">Dataset</th>
<th rowspan="2">Size</th>
<th colspan="2">Video</th>
<th colspan="2">Query</th>
<th colspan="4">Response</th>
</tr>
<tr>
<th>Obs.</th>
<th>Fut.</th>
<th>OEQ</th>
<th>MCQ</th>
<th>Observation</th>
<th>Reasoning</th>
<th>Prediction</th>
<th>Answer</th>
</tr>
</thead>
<tbody>
<tr>
<td>D1</td>
<td>42,673</td>
<td colspan="2">Unpartitioned</td>
<td>—</td>
<td>—</td>
<td colspan="4">Caption</td>
</tr>
<tr>
<td>D2</td>
<td>15,290</td>
<td>✓</td>
<td>✓</td>
<td>✓</td>
<td>—</td>
<td>✓</td>
<td>✓</td>
<td>✓</td>
<td>—</td>
</tr>
<tr>
<td>D3</td>
<td>2,885</td>
<td>✓</td>
<td>—</td>
<td>—</td>
<td>✓</td>
<td>✓</td>
<td>✓</td>
<td>✓</td>
<td>✓</td>
</tr>
</tbody>
</table>
Size is the number of samples. Obs. and Fut. denote observed and future video segments. OEQ and MCQ denote open-ended and multiple-choice questions. D1 video segments are not assigned observed or future roles; each response is a caption.
## Directory structure
```text
ALWM_data/
├── README.md
├── D1/
│ ├── D1_metadata.json
│ └── videos/
├── D2/
│ ├── D2_metadata.json
│ └── videos/
└── D3/
├── D3_metadata.json
└── videos/
```
| Dataset | Metadata | Videos |
| --- | --- | --- |
| D1 | `D1/D1_metadata.json` | `D1/videos/` |
| D2 | `D2/D2_metadata.json` | `D2/videos/` |
| D3 | `D3/D3_metadata.json` | `D3/videos/` |
Video files are grouped into numbered subdirectories inside `videos/`; the exact path is given in the metadata.
## Metadata format
Each metadata file is a JSON object keyed by sample ID. Every entry contains only `video`, `query`, and `answer`.
| Field | Meaning |
| --- | --- |
| Sample ID (object key) | Unique identifier of the sample within the dataset. |
| `video` | Video path relative to the repository root. For D2, an object containing the `observation` and `future` video paths. |
| `query` | Question text. Empty for D1; an open-ended question for D2; a question with its choices for D3. |
| `answer` | Complete response as a single text string. Original text, tags, line breaks, and tag order are preserved; the response is not split into separate fields. |
The examples below illustrate the structure; ellipses stand for sample text.
### D1
`D1/D1_metadata.json` maps each sample ID to its video segment, an empty query, and a caption.
```json
{
"D1_example": {
"video": "D1/videos/000/D1_example.mp4",
"query": "",
"answer": "..."
}
}
```
### D2
`D2/D2_metadata.json` maps each sample ID to its observed and future video segments, an open-ended question, and the complete response text.
```json
{
"D2_example": {
"video": {
"observation": "D2/videos/000/D2_example_observation.mp4",
"future": "D2/videos/000/D2_example_future.mp4"
},
"query": "...",
"answer": "<observation>...</observation>\n<reasoning>...</reasoning>\n<latent></latent>\n<prediction>...</prediction>"
}
}
```
### D3
`D3/D3_metadata.json` maps each sample ID to its observed video segment, a multiple-choice question including its choices, and the complete response text.
```json
{
"D3_example": {
"video": "D3/videos/000/D3_example.mp4",
"query": "...\n\nOptions:\nA. ...\nB. ...\nC. ...\nD. ...",
"answer": "<observation>...</observation>\n<reasoning>...</reasoning>\n<latent></latent>\n<prediction>...</prediction><answer>...</answer>"
}
}
```
|