Claude vs ChatGPTSame prompts, side by side.

Opus 5.5

51 words · Unedited API response

QA found yesterday that the export drops the timezone on some dates, so we will not ship on Tuesday as planned. We now plan to ship on Thursday, provided Leon reviews Mira's fix by noon Wednesday and QA verifies it by 5 p.m. Wednesday. Please inform support of the change today.

GPT 6.1 Sol

53 words · Unedited API response

QA discovered yesterday that the export drops the timezone on some dates, so we will not ship on Tuesday as previously planned. We now plan to ship on Thursday, provided Leon reviews Mira’s fix by noon Wednesday and QA verifies it by 5 p.m. Wednesday. Please inform support of the schedule change today.

Opus 5.5

75 words · Unedited API response

- **Source of authority:** "We the People of the United States" ordain and establish the Constitution.
- **Unity and justice:** It aims to form "a more perfect Union" and "establish Justice."
- **Peace and security:** It seeks to "insure domestic Tranquility" and "provide for the common defence."
- **Public well-being:** It intends to "promote the general Welfare."
- **Lasting liberty:** It aims to "secure the Blessings of Liberty" for the present generation and its "Posterity."

GPT 6.1 Sol

59 words · Unedited API response

- The people establish the Constitution for the United States of America to form a more perfect Union.
- They seek to establish justice and ensure domestic tranquility.
- They aim to provide for the common defense.
- They seek to promote the general welfare.
- They aim to secure the blessings of liberty for themselves and future generations.

Opus 5.5

67 words · Unedited API response

```python
def merge_intervals(intervals):
    for start, end in intervals:
        if start >= end:
            raise ValueError(f"Invalid interval: ({start}, {end}); start must be less than end")

    if not intervals:
        return []

    sorted_intervals = sorted(intervals)
    merged = []
    cur_start, cur_end = sorted_intervals[0]

    for start, end in sorted_intervals[1:]:
        if start < cur_end:
            if end > cur_end:
                cur_end = end
        else:
            merged.append((cur_start, cur_end))
            cur_start, cur_end = start, end

    merged.append((cur_start, cur_end))
    return merged
```

Python checks: 9/9 passed

GPT 6.1 Sol

45 words · Unedited API response

```python
def merge_intervals(intervals):
    for start, end in intervals:
        if start >= end:
            raise ValueError("Interval start must be less than end")

    merged = []
    for start, end in sorted(intervals):
        if merged and start < merged[-1][1]:
            merged[-1] = (merged[-1][0], max(merged[-1][1], end))
        else:
            merged.append((start, end))

    return merged
```

Python checks: 9/9 passed

Opus 5.5

46 words · Unedited API response

**Calculation:**

1. Initial bookings: 3/5 × 240 = **144** seats
2. After changes: 144 − 18 + 37 = **163** attendee bookings
3. Seats taken in total: 163 attendees + 12 crew = **175**
4. Seats still available: 240 − 175 = **65**

Answer: 65 seats

Final answer: 65 seats · Correct on this problem

GPT 6.1 Sol

34 words · Unedited API response

Initially booked: \(240 \times \frac{3}{5} = 144\) seats.  
Updated bookings: \(144 - 18 + 37 = 163\) seats.  
Available after reserving crew seats: \(240 - 163 - 12 = 65\) seats.

Answer: 65 seats

Final answer: 65 seats · Correct on this problem

Opus 5.5

136 words · Unedited API response

A database table is like a huge spreadsheet. Say you want every order from the customer "Acme." Normally the database reads every row from top to bottom, like scrolling through a million-row sheet looking for matches.

An index is a separate, sorted lookup list, like the index at the back of a book. An index on the CustomerName column lists each name alphabetically, with pointers to the exact rows where it appears. The database can jump straight to "Acme" and grab only those rows, turning a slow, full-table search into a near-instant lookup.

The cost is that every time a row is added, changed, or deleted, the database must also update the index to keep it sorted. Indexes make reading faster but writing slower. That's why you index the columns people search often, not every column.

GPT 6.1 Sol

114 words · Unedited API response

A database index is a shortcut that helps a database find records without checking every row. Think of it as a searchable guide to a spreadsheet: it stores selected values alongside pointers to the rows containing them.

For example, imagine an orders table with one million rows and columns for order number, customer, and date. To find order #58241 without an index, the database might check rows one by one. An index on the order-number column lets it locate that order much faster.

One cost is slower updates: whenever an order number is added or changed, the database must update both the table and its index. Indexes help searches, but maintaining them adds work.