LSL / EVALUATION ARCHIVE

AI TRAINER & LLM EVALUATOR

LorenzzoSanthiago Lima

14 months of freelance work at RWS, reviewing prompts, model claims, conversation context, and transcriptions.

FLORIANÓPOLIS, BRAZIL

SELECTED WORK / FIVE SIMULATIONS

Evaluation archive

Fictional inputs. Each case shows the evidence and the reasoning behind the review.

CONTEXT RETENTION

The meeting moved.

User update

The user originally wanted a short, informal message to Marina confirming Thursday at 2 p.m., with no emoji.

“It’s moved to Friday at 10 a.m. Keep everything else the same.”

Model reply

“Hey, Marina! Confirming our meeting for Thursday at 2 p.m. See you then!”

The tone and length fit. The time is stale.

Review

− Thursday at 2 p.m.+ Friday at 10 a.m.

Use the corrected time. Keep the recipient, informal tone, and no-emoji instruction.

FACTUAL ACCURACY

A refund request becomes a guarantee.

Input

The customer bought the item 12 days ago. The policy allows requests within 14 calendar days. Approved refunds are usually processed within five business days.

“Yes, your refund is guaranteed and will be in your account in five calendar days.”

Review

The customer can still submit a request. The policy makes approval conditional, measures processing in business days, and gives no date for the deposit.

“Yes, you can still request a refund. If it’s approved, processing usually takes up to five business days.”

PROMPT RANKING

A billing handoff needs a next step.

Prompt A

“Summarize the support conversation and explain what happened.”

Prompt B

“Summarize the conversation in up to three bullets for the billing team. Include the issue, what support checked, and the next action. Mark missing information as ‘not provided.’”

Review

Prefer B. It identifies who will use the summary and what they need. If support never checked the charge, B gives the model a way to mark the gap without filling it in.

TRANSCRIPTION REVIEW

The speaker corrects the day.

Mock speech reference

“I sent it on Tuesday… I mean, on Wednesday, to [inaudible].”

Candidate transcript

“I sent it on Tuesday to the finance team.”

Review

The brief calls for preserving self-corrections and marking unclear speech. Restore “I mean, on Wednesday” and keep “[inaudible]”. The reference never establishes the recipient.

REVIEWER DISAGREEMENT

A direct reply makes an unsupported promise.

Order record

A shipping label was created. There is no carrier scan or delivery estimate.

Competing replies

A — “Yes, it will arrive tomorrow. A tracking number has already been created.”
B — “The shipping label has been created. There’s no delivery estimate yet.”

Calibration note

A answers directly, but B is the better choice when factual accuracy takes priority. Use B as the reference here and test the rule on an order where the carrier actually provides an estimate. If the rubric leaves the priority unclear, ask the project lead to resolve it before adding the case to the reference set.

PROFESSIONAL EXPERIENCE

RWS / Freelance

14 months at RWS

Ranked prompts, checked claims in model responses, reviewed multi-turn conversations for context retention, and transcribed material for AI training.

Brazilian Portuguese · Native
English · Fluent