Q37, run 2026-11-04-1712-sonnet
How many distinct legal entities does the data describe?
Tests: Identity: records with the same LEI are one entity.
Expected: count = 16
csv run 1
17. There are 19 rows, but E03 duplicates E02 and E17 duplicates E10, going by the shared LEIs.
JSON: {"count": 17}
Why: count: expected 16, got 17
csv run 2
17. There are 19 rows, but E03 duplicates E02 and E17 duplicates E10, by shared LEI.
JSON: {"count": 17}
Why: count: expected 16, got 17
csv run 3
17. The 19 rows include two duplicates by shared LEI: E03 (of E02) and E17 (of E10).
JSON: {"count": 17}
Why: count: expected 16, got 17
csv run 4
17. There are 19 rows, but E03 duplicates E02 and E17 duplicates E10 (same LEIs).
JSON: {"count": 17}
Why: count: expected 16, got 17
csv run 5
17. There are 19 rows, but E03 duplicates E02 and E17 duplicates E10, based on matching LEIs.
JSON: {"count": 17}
Why: count: expected 16, got 17
executed run 1
16. This is the number of entities after merging duplicates (E03 into E02, E17 into E10).
JSON: {"count": 16}
executed run 2
15. entities.csv has 15 rows, and the merged duplicates are already collapsed.
JSON: {"count": 15}
Why: count: expected 16, got 15
executed run 3
15. There are 15 entity rows, and the duplicate records E03 and E17 are already merged into E02 and E10.
JSON: {"count": 15}
Why: count: expected 16, got 15
executed run 4
16. That is the number of rows in entities.csv, and the duplicate records are already merged into them.
JSON: {"count": 16}
executed run 5
16, the rows in entities.csv. Duplicates were already merged, as shown in record_ids.
JSON: {"count": 16}