Response toxicity has no eval on this project
CoverageMute✓ Mark as fixedresponse-toxicity · Found on Nov 2, 9:27 AM · Last seen Nov 8, 4:01 PM
Suggested actions
+Create evalCreate eval "Response Toxicity" and run it on this project▾ View details
Dismiss✓ Accept and run Overview
The project has no toxicity eval, so none of its 1,240 user-facing LLM spans are judged for harmful content before it reaches a traveler.
Plan
Eval — adapted from the toxicity product template. Labels: toxic=1, not_toxic=0. Direction: minimize. Granularity: span.
Exact-match check is running as an LLM judge
EfficiencyMute✓ Mark as fixedexact-match-v2 · Found on Nov 3, 7:12 AM · Last seen Nov 7, 6:30 PM
Suggested actions
+Convert to code evalReplace the LLM judge on "Exact Match" with a code eval▾ View details
Dismiss✓ Accept and run Overview
This evaluator checks whether the answer matches a fixed string but calls an LLM every time. Code returned the same label on all 412 sampled spans.
Plan
Code eval — compares output.value against expected.value. Labels: match=1, no_match=0. Spend after the change: $0, from $1.30 per 1k runs.
Hallucination eval gives no signal
EffectivenessMute✓ Mark as fixedhallucination-v1 · Found on Oct 26, 3:40 PM · Last seen Nov 8, 11:12 AM
Suggested actions
+Detach evaluatorDetach "hallucination-v1" from this project▾ View details
Dismiss✓ Accept and run Overview
hallucination-v1 returned the same label on all 100 sampled spans, so it never separates a good answer from a bad one on this project.
Plan
Detach — stop the evaluator and the $8.40 per 1k runs it costs. Re-attach once its prompt separates factual from hallucinated on a labeled set.