Annotation Language Cheat Sheet #6

Open
opened 2025年12月31日 09:00:12 +01:00 by code_macabre · 0 comments

HIGH-QUALITY ANNOTATION LANGUAGE — CHEAT SHEET

You don’t invent sentences in annotation.
You assemble them.


1️⃣ Universal sentence starters (use freely)

These are gold. Platforms love them.

  • "The text is clear because..."
  • "The paragraph presents..."
  • "The wording is simple and direct..."
  • "The content follows a logical structure..."
  • "The explanation focuses on..."

If you ever feel stuck, start with one of these.


2️⃣ Clarity justification phrases

Use structure, not feelings.

Good phrases:

  • "uses simple and direct sentences"
  • "presents one main idea per sentence"
  • "maintains a clear cause-and-effect relationship"
  • "progresses logically from problem to solution"
  • "avoids ambiguous or technical terms"

Avoid:

  • "easy to read"
  • "nice"
  • "good"
  • "relatable"

3️⃣ Flow & organization language

Annotation-approved ways to say "it flows well":

  • "The ideas are logically ordered."
  • "Each sentence builds on the previous one."
  • "The paragraph maintains a consistent focus."
  • "There are no abrupt topic shifts."

4️⃣ Neutrality & tone (very important)

Use these when judging bias or emotion:

  • "The tone is neutral and informational."
  • "The text avoids emotional or persuasive language."
  • "The wording does not express personal opinions."
  • "The content presents information without judgment."

Never say you agree or disagree.


5️⃣ Pointing out weaknesses (without sounding critical)

This is a key skill.

Safe phrasing:

  • "Clarity may be reduced because..."
  • "The explanation lacks specific examples..."
  • "Some terms are not clearly defined..."
  • "The main idea could be stated more explicitly..."

Notice the soft language: may, could.


6️⃣ Suggested improvement templates

Only one action, never creative.

  • "Clarity could be improved by adding a brief example."
  • "The main idea could be stated more explicitly in the first sentence."
  • "Defining key terms could improve understanding."
  • "No improvement needed."

That’s it. Stop there.


7️⃣ Rating justification (copy-paste friendly)

Use this exact pattern:

"I rated the text X/5 because [strength], but [minor limitation]."

Examples:

  • "I rated the text 4/5 because the sentences are clear and logically ordered, but the lack of examples slightly limits clarity."
  • "I rated the text 5/5 because the wording is simple, focused, and easy to follow."

8️⃣ Words to prefer vs avoid

Prefer:

  • clear
  • logical
  • structured
  • consistent
  • specific
  • neutral

Avoid:

  • nice
  • good
  • bad
  • interesting
  • important
  • relatable

These trigger reviewer skepticism.


🧠 The single rule to remember

Describe properties of the text, not your reaction to it.

If a sentence sounds like your opinion, rewrite it.


Your readiness check (honest)

# ⚓ HIGH-QUALITY ANNOTATION LANGUAGE — CHEAT SHEET You don’t *invent* sentences in annotation. You **assemble** them. --- ## 1️⃣ Universal sentence starters (use freely) These are gold. Platforms love them. * "The text is clear because..." * "The paragraph presents..." * "The wording is simple and direct..." * "The content follows a logical structure..." * "The explanation focuses on..." If you ever feel stuck, start with one of these. --- ## 2️⃣ Clarity justification phrases Use **structure**, not feelings. ✅ Good phrases: * "uses simple and direct sentences" * "presents one main idea per sentence" * "maintains a clear cause-and-effect relationship" * "progresses logically from problem to solution" * "avoids ambiguous or technical terms" ❌ Avoid: * "easy to read" * "nice" * "good" * "relatable" --- ## 3️⃣ Flow & organization language Annotation-approved ways to say "it flows well": * "The ideas are logically ordered." * "Each sentence builds on the previous one." * "The paragraph maintains a consistent focus." * "There are no abrupt topic shifts." --- ## 4️⃣ Neutrality & tone (very important) Use these when judging bias or emotion: * "The tone is neutral and informational." * "The text avoids emotional or persuasive language." * "The wording does not express personal opinions." * "The content presents information without judgment." Never say you *agree* or *disagree*. --- ## 5️⃣ Pointing out weaknesses (without sounding critical) This is a key skill. Safe phrasing: * "Clarity may be reduced because..." * "The explanation lacks specific examples..." * "Some terms are not clearly defined..." * "The main idea could be stated more explicitly..." Notice the **soft language**: *may, could*. --- ## 6️⃣ Suggested improvement templates Only **one action**, never creative. * "Clarity could be improved by adding a brief example." * "The main idea could be stated more explicitly in the first sentence." * "Defining key terms could improve understanding." * "No improvement needed." That’s it. Stop there. --- ## 7️⃣ Rating justification (copy-paste friendly) Use this exact pattern: > "I rated the text X/5 because [strength], but [minor limitation]." Examples: * "I rated the text 4/5 because the sentences are clear and logically ordered, but the lack of examples slightly limits clarity." * "I rated the text 5/5 because the wording is simple, focused, and easy to follow." --- ## 8️⃣ Words to **prefer** vs **avoid** ### Prefer: * clear * logical * structured * consistent * specific * neutral ### Avoid: * nice * good * bad * interesting * important * relatable These trigger reviewer skepticism. --- ## 🧠 The single rule to remember > **Describe properties of the text, not your reaction to it.** If a sentence sounds like *your opinion*, rewrite it. --- ## ⚓ Your readiness check (honest)
Sign in to join this conversation.
No Branch/Tag specified
No results found.
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
code_macabre/My_Notes#6
Reference in a new issue
code_macabre/My_Notes
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?