From 4569db94555409393bb012cb50b0e5cf9e8b5bc5 Mon Sep 17 00:00:00 2001
From: Daniel Kleine <53251018+d-kleine@users.noreply.github.com>
Date: Tue, 17 Dec 2024 18:44:05 +0100
Subject: [PATCH] fix: assigning score column (#5749)

---
 docs/evaluation/how-to-evals/evaluating-phoenix-traces.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/evaluation/how-to-evals/evaluating-phoenix-traces.md b/docs/evaluation/how-to-evals/evaluating-phoenix-traces.md
index 4e0ef65de3..ca19a0ab16 100644
--- a/docs/evaluation/how-to-evals/evaluating-phoenix-traces.md
+++ b/docs/evaluation/how-to-evals/evaluating-phoenix-traces.md
@@ -160,7 +160,7 @@ We now have a DataFrame with a column for whether each joke is a repeat of a pre
 Our evals\_df has a column for the span\_id and a column for the evaluation result. The span\_id is what allows us to connect the evaluation to the correct trace in Phoenix. Phoenix will also automatically look for columns named "label" and "score" to display in the UI.
 
 ```python
-eval_df["score"] = eval_df["label"].astype(int)
+eval_df["score"] = eval_df["score"].astype(int)
 eval_df["label"] = eval_df["label"].astype(str)
 ```