NeutralEye

How to read the analysis

A guide to interpreting what NeutralEye found — what the direction label means, how to weigh the confidence score, and where the analysis has limits worth keeping in mind.

Direction label

What the label means

The direction label describes the dominant pattern of signals found in the text — not a political verdict on the subject, outlet, or author. The same outlet can receive different labels across different articles.

Left-leaningCenterRight-leaning

Left-leaning

Signals — tone, framing, sourcing, and omission — consistently pointed in a direction associated with left-of-center interpretation. This describes the pattern found in the text, not a judgment about the subject matter.

Center

Signals were balanced, contradictory, or too sparse for a clear directional pattern. A center result does not certify fairness — it means the analysis did not detect a dominant lean.

Right-leaning

Signals consistently pointed in a direction associated with right-of-center interpretation. Same rules apply: the label describes what was found in this specific text, not the outlet or author overall.

Confidence score

Signal consistency, not truth

Confidence measures how clearly and consistently bias signals appeared across the submitted text — not whether the article is factually accurate or the journalist intended to mislead.

High confidence

The same signal pattern repeated consistently across most of the article — tone, framing, and sourcing all pointed the same way. A well-written opinion column can score high confidence because its structure is deliberately consistent.

Low confidence

Signals were mixed, thin, or contradictory. This can mean the article is genuinely balanced — but it can also mean the text was too short, the writing was inconsistent, or the story was still developing when it was filed.

How to use it

Judgment comes first

NeutralEye works best when the result is read as an analytical aid — summary first, evidence second, wider context whenever the story feels incomplete.

01

Start with the summary

Read the top-level explanation first, then use the supporting sections to see what language and sourcing patterns shaped the result.

02

Use examples as evidence

Quoted examples show the exact phrases or structures that triggered concern — not isolated proof by themselves. Check them against the article.

03

Treat recommendations as prompts

When the system suggests more reading, it's flagging a gap in context — not declaring the question settled.

Where the analysis has limits

Messy input

Very short passages, failed extraction, navigation text, or blocked pages can weaken the read significantly.

Rhetorical edge cases

Satire, irony, or unusual writing style can resemble bias signals even when the intent is clearly different.

Scope of the result

The result reflects patterns in this submitted text — not a universal judgment on the outlet, author, or topic.

Reader judgment

The analysis is one data point. It works best as a prompt to slow down and inspect — not as a substitute for forming your own view.

Try it on a real article

Open Analyzer