Which Set Of Coordinates Represents A Function

You're staring at a set of ordered pairs on a homework problem. {(1, 2), (2, 4), (3, 6), (4, 8)}. Looks like a function, right? Plus, then you see {(1, 2), (2, 4), (1, 5), (3, 6)} and something feels off. But why exactly?

Most students memorize the vertical line test and call it a day. But the coordinate-level reasoning — the actual definition* — gets fuzzy fast. And that fuzziness shows up later when you're dealing with piecewise functions, inverse relations, or discrete data sets in statistics.

Let's clear it up once and for all.

What Is a Function, Really?

At its core, a function is a rule of assignment. That's why you give it an input, it gives you exactly one* output. Not zero. Not two. One.

In coordinate terms: a set of ordered pairs (x, y) represents a function if and only if no two pairs share the same x-value with different y-values.

That's it. That's the whole definition.

The x-values are your domain* — the inputs. Day to day, the y-values are your range* — the outputs. For every x in the domain, there's a single, unambiguous y paired with it.

The "One Input, One Output" Rule

Think of it like a vending machine. Every time. You press A1 (input). Even so, you get a Coke (output). If sometimes you got a Coke and sometimes a Sprite from the same button, the machine is broken — it's not functioning as a function.

Mathematically: if (a, b) and (a, c) are both in your set, then b must equal c. Otherwise, it's not a function.

Relations vs. Functions

Every set of ordered pairs is a relation*. A function is just a special kind* of relation — one that follows the single-output rule.

All functions are relations. Not all relations are functions.

Why It Matters / Why People Care

You might wonder: why does this distinction matter? Isn't it just vocabulary?

It matters because functions are predictable. That said, that predictability is what lets us do calculus, build models, write code, and solve equations. If a relation isn't a function, you can't reliably invert it, differentiate it, or compose it with other functions.

Real-World Stakes

Programming: A function in code must* return one value for a given input. If your mapping allows multiple outputs, your code has a bug.
Data analysis: When you're fitting a regression line, you're assuming a functional relationship — one y per x. Duplicate x's with different y's? That's noise, not a clean function.
Physics: Position as a function of time. At any given moment, an object is in one place. Not two.

The Vertical Line Test — And Why It Works

You've seen this: graph the points. Draw vertical lines. If any vertical line hits more than one point, it's not a function.

Why vertical? If it hits two points, that x has two different y's. That's why because a vertical line represents a constant x-value*. Definition violated.

The test is just the definition, visualized.

How to Check a Set of Coordinates

Let's get practical. Here's your step-by-step process.

Step 1: List the x-Values

Write down every first coordinate. Just the x's.

Set A: {(1, 2), (2, 4), (3, 6), (4, 8)} → x-values: 1, 2, 3, 4
Set B: {(1, 2), (2, 4), (1, 5), (3, 6)} → x-values: 1, 2, 1, 3

Step 2: Check for Repeats

Scan the list. Any duplicates?

Set A: all unique. Set B: 1 appears twice. Which means good so far. Flag it.

Step 3: Compare the Corresponding y-Values

For each repeated x, look at the y's paired with it.

Set B: x = 1 pairs with y = 2 and y = 5. On top of that, different y's. **Not a function.

Want to learn more? We recommend hund's rule pauli exclusion principle aufbau principle and the loudness of sound is measured in for further reading.

That's the whole algorithm. Takes ten seconds once you're used to it.

Worked Examples

Example 1
{(-2, 4), (-1, 1), (0, 0), (1, 1), (2, 4)}
x-values: -2, -1, 0, 1, 2 → all unique → Function
(Notice the y-values repeat. That's fine. Functions can share outputs. They just can't share inputs with different outputs.)

Example 2
{(0, 0), (0, 1), (0, -1), (1, 2)}
x-values: 0, 0, 0, 1 → 0 repeats three times
y-values for x=0: 0, 1, -1 → all different → Not a function

Example 3
{(3, 7), (3, 7), (5, 9)}
x-values: 3, 3, 5 → 3 repeats
y-values for x=3: 7, 7 → same* y → Function
Duplicate pairs* don't break anything. Only conflicting pairs do.

Example 4 — The tricky one
{(x, y) | y² = x, x ≥ 0} written as coordinates: (0, 0), (1, 1), (1, -1), (4, 2), (4, -2)...
x = 1 maps to 1 and -1. x = 4 maps to 2 and -2. Not a function.
This is the relation y = ±√x. The square root function* is just the top half (y = √x).

Common Mistakes / What Most People Get Wrong

Mistake 1: Confusing "Unique y" with "Unique x"

Students often think: "All the y-values must be different.That's a one-to-one* function (injective), which is a stricter condition. In real terms, " Nope. A regular function just needs unique x → y mapping.

{(1, 5), (2, 5), (3, 5)} is a perfectly good function. Constant function. Boring, but valid.

Mistake 2: Thinking a "Gap" in x-Values Breaks It

{(1, 2), (5, 10), (100, 200)} — x jumps from 1 to 5 to 100. Still a function. The domain doesn't need to be continuous. It just needs to be well-defined.

Mistake 3: Assuming Graphs Must Be "Connected"

A function can be a scatter plot. Discrete points. No lines connecting them. As long as the vertical line test passes, it's a function. The "curve" you draw in algebra class is just infinitely many* points satisfying a rule — but a finite set of points can be a function too.

Mistake 4: Confusing the Set with the Rule*

The set {(1, 2), (2, 4), (3, 6)} represents* the function f(x) = 2

x. But the rule* f(x) = 2x defines infinitely more points beyond those three. On top of that, a function can be represented by a finite set of ordered pairs, or by an algebraic expression, or by a graph, or by a table — they're all equivalent representations of the same underlying relationship. Don’t confuse the representation with the concept.

Why This Matters

Understanding whether something is a function isn’t just busywork. It’s the difference between a reliable model and a broken one.

If you’re building a calculator app and your pricing function returns two different prices for the same input, you’ve got a bug. Functions enforce consistency: one input, one output. If your physics simulation lets position map to two different velocities at the same time, you’ve broken reality. Always.

This shows up everywhere:

Databases: Primary keys must be unique (function-like behavior)
Programming: Pure functions in functional programming
Physics: Position as a function of time — an object can’t be in two places at once
Economics: Demand as a function of price — higher prices shouldn’t give conflicting quantities

Quick Reference: The Function Check

Extract all x-values
Look for duplicates
For any duplicate x, check if the y-values match
If any x has multiple different y-values → not a function

That’s it. Master this, and you’ve unlocked a fundamental tool for modeling how the world works.