Update README.md
Browse files
README.md
CHANGED
|
@@ -20,7 +20,7 @@ compatible with inverted indexing (e.g., Lucene/Elasticsearch).
|
|
| 20 |
Because each non-zero weight corresponds to a Korean subword/token,
|
| 21 |
interpretability is built-in: you can inspect which tokens drive retrieval.
|
| 22 |
|
| 23 |
-
## Why SPLADE for
|
| 24 |
- **Inverted Index Ready**: Directly index weighted tokens in standard IR stacks (Lucene/Elasticsearch).
|
| 25 |
- **Interpretable by Design**: Top-k contributing tokens per query/document explain *why* a hit matched.
|
| 26 |
- **Production-Friendly**: Fast candidate generation at web scale; memory/latency tunable via sparsity thresholds.
|
|
|
|
| 20 |
Because each non-zero weight corresponds to a Korean subword/token,
|
| 21 |
interpretability is built-in: you can inspect which tokens drive retrieval.
|
| 22 |
|
| 23 |
+
## Why SPLADE for Search?
|
| 24 |
- **Inverted Index Ready**: Directly index weighted tokens in standard IR stacks (Lucene/Elasticsearch).
|
| 25 |
- **Interpretable by Design**: Top-k contributing tokens per query/document explain *why* a hit matched.
|
| 26 |
- **Production-Friendly**: Fast candidate generation at web scale; memory/latency tunable via sparsity thresholds.
|