When we think about structured data, we generally think in terms of rows. Take this simple CSV file, which records some data about bike rides on a bike-sharing app in New York City:

CSV

ride_id, started_at,        start_area,         bike_type, duration_min
   1001, 2026-11-02 07:58,  Tribeca,            classic,             14
   1002, 2026-11-02 08:01,  Financial District, electric,             6
   1003, 2026-11-02 08:01,  SoHo,               classic,             21
   1004, 2026-11-02 08:03,  Financial District, electric,             8
   1005, 2026-11-02 08:04,  Financial District, classic,             15
   1006, 2026-11-02 08:07,  Tribeca,            electric,             1
   1007, 2026-11-02 08:08,  Tribeca,            electric,             9
   1008, 2026-11-02 08:12,  Financial District, classic,             31

Data in this CSV file is organized into rows, where each row corresponds to a record of data. Each record here is one ride, or one "thing", with everything we know about it on one line. We tend to organize data like this almost everywhere: think of spreadsheets, JSON objects, C-style structs in an array, SQL tables, etc. This is because it matches how we think: one "thing", and all of the details of that "thing".