Q1, run 2026-11-05-1234-sonnet

← back to the run

How many distinct people do the author records named "Mara Ellison", "M. Ellison" and "Ellison, Mara J." stand for?

Tests: Identity: A01, A02 and A03 share an ORCID; A04, also 'M. Ellison', has another.

Expected: count = 2

❌ R1 csv run 1 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229. A04 is a different person.

JSON: {"count": 1}

Why: count: expected 2, got 1

❌ R1 csv run 2 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229, so they are one person. A04 is a different "M. Ellison" with another ORCID.

JSON: {"count": 1}

Why: count: expected 2, got 1

✅ R1 csv run 3 graded by code

2. A01, A02 and A03 share ORCID 0000-0002-9841-6229, so they are one person. The other "M. Ellison" (A04) has a different ORCID.

JSON: {"count": 2}

❌ R1 csv run 4 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229. The other "M. Ellison" (A04) has a different ORCID.

JSON: {"count": 1}

Why: count: expected 2, got 1

❌ R1 csv run 5 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229. A04 ("M. Ellison") has a different ORCID, so it is a different person.

JSON: {"count": 1}

Why: count: expected 2, got 1

❌ R2 rdf run 1 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229. A04 is a different "M. Ellison" with a different ORCID.

JSON: {"count": 1}

Why: count: expected 2, got 1

❌ R2 rdf run 2 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229. A04 "M. Ellison" has a different ORCID, so it is not part of this group.

JSON: {"count": 1}

Why: count: expected 2, got 1

✅ R2 rdf run 3 graded by code

2. A01, A02 and A03 share ORCID 0000-0002-9841-6229, so they are one person. A04 ("M. Ellison") has a different ORCID, so it is a different person.

JSON: {"count": 2}

✅ R2 rdf run 4 graded by code

2. A01, A02 and A03 share ORCID 0000-0002-9841-6229, while A04 "M. Ellison" has a different ORCID.

JSON: {"count": 2}

✅ R2 rdf run 5 graded by code

2. A01, A02 and A03 share ORCID 0000-0002-9841-6229, so they are one person. A04 ("M. Ellison") has a different ORCID, so she is a second person.

JSON: {"count": 2}

❌ R6 rdf+ontology run 1 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229, while A04 "M. Ellison" has a different ORCID and is another person.

JSON: {"count": 1}

Why: count: expected 2, got 1

✅ R6 rdf+ontology run 2 graded by code

2. A01, A02 and A03 share ORCID 0000-0002-9841-6229, so they are one person. A04 ("M. Ellison") has a different ORCID (0000-0004-8662-8360), so she is a second person.

JSON: {"count": 2}

❌ R6 rdf+ontology run 3 graded by code

1. A01, A02 and A03 all carry ORCID 0000-0002-9841-6229, so they are one person. A04 "M. Ellison" has a different ORCID and is not part of this group.

JSON: {"count": 1}

Why: count: expected 2, got 1

❌ R6 rdf+ontology run 4 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229. A04 "M. Ellison" has a different ORCID, so it is someone else.

JSON: {"count": 1}

Why: count: expected 2, got 1

❌ R6 rdf+ontology run 5 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229. A04 "M. Ellison" has a different ORCID and is not counted.

JSON: {"count": 1}

Why: count: expected 2, got 1

❌ R5 csv+ontology run 1 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229, so they are one person (A04 has a different ORCID).

JSON: {"count": 1}

Why: count: expected 2, got 1

✅ R5 csv+ontology run 2 graded by code

2. A01, A02 and A03 share ORCID 0000-0002-9841-6229, so they are one person. The name "M. Ellison" also covers A04, who has a different ORCID and is a second person.

JSON: {"count": 2}

❌ R5 csv+ontology run 3 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229, so they are one person. A04 ("M. Ellison") has a different ORCID.

JSON: {"count": 1}

Why: count: expected 2, got 1

❌ R5 csv+ontology run 4 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229, so they are one person. A04 is a different ORCID.

JSON: {"count": 1}

Why: count: expected 2, got 1

❌ R5 csv+ontology run 5 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229, so they are one person. A04 ("M. Ellison") has a different ORCID.

JSON: {"count": 1}

Why: count: expected 2, got 1

❌ R4 csv+markdown run 1 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229, so they are one person.

JSON: {"count": 1}

Why: count: expected 2, got 1

❌ R4 csv+markdown run 2 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229. A04 (also "M. Ellison") has a different ORCID and is not included.

JSON: {"count": 1}

Why: count: expected 2, got 1

❌ R4 csv+markdown run 3 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229. A04 ("M. Ellison") has a different ORCID.

JSON: {"count": 1}

Why: count: expected 2, got 1

❌ R4 csv+markdown run 4 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229. A04 has a different ORCID and is a different person.

JSON: {"count": 1}

Why: count: expected 2, got 1

✅ R4 csv+markdown run 5 graded by code

2. A01, A02 and A03 share ORCID 0000-0002-9841-6229 and are one person. The name "M. Ellison" also covers A04 (ORCID ...8360), a different person.

JSON: {"count": 2}

❌ R3 csv+padding run 1 graded by code

1. A01, A02 and A03 share one ORCID; A04 has a different one.

JSON: {"count": 1}

Why: count: expected 2, got 1

✅ R3 csv+padding run 2 graded by code

2. A01, A02 and A03 share ORCID 0000-0002-9841-6229, while A04 ("M. Ellison") has a different ORCID.

JSON: {"count": 2}

❌ R3 csv+padding run 3 graded by code

1. A01, A02 and A03 share ORCID 0000-0002-9841-6229, while A04 has a different ORCID.

JSON: {"count": 1}

Why: count: expected 2, got 1

✅ R3 csv+padding run 4 graded by code

2. A01, A02 and A03 share ORCID 0000-0002-9841-6229, so they are one person. A04 ("M. Ellison") has a different ORCID, so it is a second person.

JSON: {"count": 2}

✅ R3 csv+padding run 5 graded by code

2. A01, A02 and A03 share ORCID 0000-0002-9841-6229. The other "M. Ellison" record, A04, has a different ORCID (0000-0004-8662-8360).

JSON: {"count": 2}

✅ R10 executed run 1 graded by code

2. A01 merges A01, A02 and A03 (the "Mara Ellison" and "Ellison, Mara J." forms), and A04 "M. Ellison" has a different ORCID and stays separate. The data doesn't show which name form belongs to A02 or A03.

JSON: {"count": 2}

✅ R10 executed run 2 graded by code

2. A01 merges A01, A02 and A03, which covers "Mara Ellison" and, presumably, "Ellison, Mara J.". A04 "M. Ellison" has a different ORCID and stays separate. The data does not show the names on A02 and A03, so the "Ellison, Mara J." match is inferred.

JSON: {"count": 2}

✅ R10 executed run 3 graded by code

2. The three records A01, A02 and A03 are merged into one person (A01), and M. Ellison (A04) is a separate person with a different ORCID. The data doesn't show which record is named "Ellison, Mara J.", so I assume it is one of A02/A03.

JSON: {"count": 2}

✅ R10 executed run 4 graded by code

2. People A01 (which merges A01, A02 and A03) and A04 are distinct (different ORCIDs). I take "Ellison, Mara J." to be one of the merged A02/A03 records, but the author-level names aren't shown.

JSON: {"count": 2}

✅ R10 executed run 5 graded by code

2. A01 merges A01, A02 and A03, which covers "Mara Ellison" and "Ellison, Mara J.". A04 "M. Ellison" has a different ORCID and is a separate person.

JSON: {"count": 2}