Cosineyx commited on
Commit
533dfbc
·
verified ·
1 Parent(s): 59c85c8

Remove category distribution tables from dataset card

Browse files
Files changed (1) hide show
  1. README.md +0 -24
README.md CHANGED
@@ -131,30 +131,6 @@ The `users` configuration contains `user_index`, `user_id`, `persona_info`, `num
131
 
132
  Alignment follows the original benchmark: dialogue record 0 corresponds to `qa_user00.json`, record 1 to `qa_user01.json`, and so on. Both tables include the original UUID to validate this join. Preserve the original trajectory/session order and source timestamps when reproducing the temporal evaluation protocol.
133
 
134
- ## Release statistics
135
-
136
- ### Query types
137
-
138
- | Original label | Instances |
139
- |---|---:|
140
- | Advice | 1,699 |
141
- | Recommendation | 455 |
142
- | Conversation | 62 |
143
-
144
- ### Logical association labels
145
-
146
- | Original label | Instances |
147
- |---|---:|
148
- | Goal/Mission Alignment | 287 |
149
- | Contextual Fit | 284 |
150
- | Other | 23 |
151
- | Resource Constraint | 134 |
152
- | Motivational Orientation | 588 |
153
- | State Constraint | 609 |
154
- | Identity Shift | 291 |
155
-
156
- These counts describe the files in this release. Category strings are preserved as released; no relabeling or reassignment is performed during Hub export. Further definitions and examples are available in the [logical association documentation](https://github.com/ThisIsCosine/IMLogic/blob/main/docs/mined_logical_associations.md).
157
-
158
  ## Source data and construction
159
 
160
  IMLogic reuses HaluMem-Medium histories and memory entries. Its construction pipeline tags memories, mines candidate logical associations, and generates QA instances through a Generator–Judger–Refiner process followed by expert screening and independent sample-based human evaluation. See the paper and repository for the construction prompts and evaluation protocols.
 
131
 
132
  Alignment follows the original benchmark: dialogue record 0 corresponds to `qa_user00.json`, record 1 to `qa_user01.json`, and so on. Both tables include the original UUID to validate this join. Preserve the original trajectory/session order and source timestamps when reproducing the temporal evaluation protocol.
133
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
134
  ## Source data and construction
135
 
136
  IMLogic reuses HaluMem-Medium histories and memory entries. Its construction pipeline tags memories, mines candidate logical associations, and generates QA instances through a Generator–Judger–Refiner process followed by expert screening and independent sample-based human evaluation. See the paper and repository for the construction prompts and evaluation protocols.