Text Generation
Transformers
Safetensors
English
t5
text2text-generation
dialogue
gricean-maxims
cooperative-communication
text-repair
seq2seq
nlp
Eval Results (legacy)
text-generation-inference
Instructions to use Pushkar27/GriceBench-Repair with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use Pushkar27/GriceBench-Repair with Transformers:
# Use a pipeline as a high-level helper from transformers import pipeline pipe = pipeline("text-generation", model="Pushkar27/GriceBench-Repair")# Load model directly from transformers import AutoTokenizer, AutoModelForSeq2SeqLM tokenizer = AutoTokenizer.from_pretrained("Pushkar27/GriceBench-Repair") model = AutoModelForSeq2SeqLM.from_pretrained("Pushkar27/GriceBench-Repair", device_map="auto") - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- vLLM
How to use Pushkar27/GriceBench-Repair with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "Pushkar27/GriceBench-Repair" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "Pushkar27/GriceBench-Repair", "prompt": "Once upon a time,", "max_tokens": 512, "temperature": 0.5 }'Use Docker
docker model run hf.co/Pushkar27/GriceBench-Repair
- SGLang
How to use Pushkar27/GriceBench-Repair with SGLang:
Install from pip and serve model
# Install SGLang from pip: pip install sglang # Start the SGLang server: python3 -m sglang.launch_server \ --model-path "Pushkar27/GriceBench-Repair" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "Pushkar27/GriceBench-Repair", "prompt": "Once upon a time,", "max_tokens": 512, "temperature": 0.5 }'Use Docker images
docker run --gpus all \ --shm-size 32g \ -p 30000:30000 \ -v ~/.cache/huggingface:/root/.cache/huggingface \ --env "HF_TOKEN=<secret>" \ --ipc=host \ lmsysorg/sglang:latest \ python3 -m sglang.launch_server \ --model-path "Pushkar27/GriceBench-Repair" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "Pushkar27/GriceBench-Repair", "prompt": "Once upon a time,", "max_tokens": 512, "temperature": 0.5 }' - Docker Model Runner
How to use Pushkar27/GriceBench-Repair with Docker Model Runner:
docker model run hf.co/Pushkar27/GriceBench-Repair
CRITICAL: Remove all escaped underscores from YAML metadata
Browse files
README.md
CHANGED
|
@@ -4,7 +4,7 @@ language:
|
|
| 4 |
license: apache-2.0
|
| 5 |
library_name: transformers
|
| 6 |
tags:
|
| 7 |
-
-
|
| 8 |
- dialogue
|
| 9 |
- gricean-maxims
|
| 10 |
- cooperative-communication
|
|
@@ -16,13 +16,13 @@ datasets:
|
|
| 16 |
- topical-chat
|
| 17 |
metrics:
|
| 18 |
- bleu
|
| 19 |
-
pipeline_tag:
|
| 20 |
base_model: google-t5/t5-base
|
| 21 |
model-index:
|
| 22 |
- name: GriceBench-Repair
|
| 23 |
results:
|
| 24 |
- task:
|
| 25 |
-
type:
|
| 26 |
name: Gricean Maxim Violation Repair
|
| 27 |
dataset:
|
| 28 |
name: Topical-Chat (GriceBench repair validation split, N=401)
|
|
@@ -161,14 +161,14 @@ Per-maxim BLEU scores on the repair validation set (N=401):
|
|
| 161 |
|
| 162 |
**Three-layer degeneracy prevention:**
|
| 163 |
1. Violation-type-aware decoding (nucleus sampling for Manner, beam for others)
|
| 164 |
-
2. Post-generation multi-signal filter
|
| 165 |
-
3. Graceful fallback
|
| 166 |
|
| 167 |
---
|
| 168 |
|
| 169 |
## Why Relation Violations Use Retrieval
|
| 170 |
|
| 171 |
-
Relation violations mean the *entire response* is off-topic — there is nothing to edit.
|
| 172 |
|
| 173 |
---
|
| 174 |
|
|
@@ -185,8 +185,7 @@ Relation violations mean the *entire response* is off-topic — there is nothing
|
|
| 185 |
|
| 186 |
## Limitations & Biases
|
| 187 |
|
| 188 |
-
- **Hallucination Risk:**
|
| 189 |
-
- **Dependency on Context:** Repair quality is heavily dependent on the provided "Context" being accurate and sufficient.
|
| 190 |
- **Mode Collapse:** Avoid using beam search for "Manner" repairs.
|
| 191 |
|
| 192 |
---
|
|
|
|
| 4 |
license: apache-2.0
|
| 5 |
library_name: transformers
|
| 6 |
tags:
|
| 7 |
+
- text-generation
|
| 8 |
- dialogue
|
| 9 |
- gricean-maxims
|
| 10 |
- cooperative-communication
|
|
|
|
| 16 |
- topical-chat
|
| 17 |
metrics:
|
| 18 |
- bleu
|
| 19 |
+
pipeline_tag: text-generation
|
| 20 |
base_model: google-t5/t5-base
|
| 21 |
model-index:
|
| 22 |
- name: GriceBench-Repair
|
| 23 |
results:
|
| 24 |
- task:
|
| 25 |
+
type: text-generation
|
| 26 |
name: Gricean Maxim Violation Repair
|
| 27 |
dataset:
|
| 28 |
name: Topical-Chat (GriceBench repair validation split, N=401)
|
|
|
|
| 161 |
|
| 162 |
**Three-layer degeneracy prevention:**
|
| 163 |
1. Violation-type-aware decoding (nucleus sampling for Manner, beam for others)
|
| 164 |
+
2. Post-generation multi-signal filter
|
| 165 |
+
3. Graceful fallback with `is_fallback: True` flag
|
| 166 |
|
| 167 |
---
|
| 168 |
|
| 169 |
## Why Relation Violations Use Retrieval
|
| 170 |
|
| 171 |
+
Relation violations mean the *entire response* is off-topic — there is nothing to edit. We route Relation repairs to a FAISS index over 50,000 Topical-Chat responses (MRR > 0.70, Top-1 accuracy > 60%).
|
| 172 |
|
| 173 |
---
|
| 174 |
|
|
|
|
| 185 |
|
| 186 |
## Limitations & Biases
|
| 187 |
|
| 188 |
+
- **Hallucination Risk:** T5 can occasionally introduce factual errors during repair. Always verify with the "Quality" detector.
|
|
|
|
| 189 |
- **Mode Collapse:** Avoid using beam search for "Manner" repairs.
|
| 190 |
|
| 191 |
---
|