Q35, run 2026-11-05-2135-haiku

← back to the run

How many entities are in the Halden group, the parent included?

Tests: Groups: membership comes from parent links, not names.

Expected: count = 3

✅ R1 csv run 1 graded by code

3
E09, E10 and E11 form the group; E17 duplicates E10's LEI.

JSON: {"count": 3}

✅ R1 csv run 2 graded by code

3 (E09, E10, E11). E17 is a duplicate of E10.

JSON: {"count": 3}

✅ R1 csv run 3 graded by code

3. The group is E09, E10 and E11. E17 is a duplicate of E10.

JSON: {"count": 3}

✅ R1 csv run 4 graded by code

3: E09, E10, and E11. E17 is a duplicate record of E10 with no parent link.

JSON: {"count": 3}

✅ R1 csv run 5 graded by code

3 (E09, E10, E11) via parent_id links.

JSON: {"count": 3}

✅ R2 rdf run 1 graded by code

3 (E09, E10, E11).

JSON: {"count": 3}

✅ R2 rdf run 2 graded by code

3 (E09, E10, E11).

JSON: {"count": 3}

✅ R2 rdf run 3 graded by code

3. The group is E09, E10 and E11.

JSON: {"count": 3}

✅ R2 rdf run 4 graded by code

3 (E09, E10, E11). E17 duplicates E10's LEI and is not counted separately.

JSON: {"count": 3}

✅ R2 rdf run 5 graded by code

3: E09, E10, E11.

JSON: {"count": 3}

✅ R6 rdf+ontology run 1 graded by code

3.
The Halden group comprises E09, E10 and E11 (E17 is the same entity as E10).

JSON: {"count": 3}

✅ R6 rdf+ontology run 2 graded by code

3. The group is E09, E10 and E11.

JSON: {"count": 3}

✅ R6 rdf+ontology run 3 graded by code

3 (E09, E10/E17, E11).

JSON: {"count": 3}

✅ R6 rdf+ontology run 4 graded by code

3: E09, E10, E11.

JSON: {"count": 3}

✅ R6 rdf+ontology run 5 graded by code

3
The Halden group is E09, E10 (the same entity as E17) and E11.

JSON: {"count": 3}

✅ R5 csv+ontology run 1 graded by code

3. E09, E10 and E11.

JSON: {"count": 3}

✅ R5 csv+ontology run 2 graded by code

3. The Halden group is E09, E10 and E11.

JSON: {"count": 3}

✅ R5 csv+ontology run 3 graded by code

3
The Halden group is E09, E10 and E11.

JSON: {"count": 3}

✅ R5 csv+ontology run 4 graded by code

3: E09, E10, E11. E17 is the same LEI as E10.

JSON: {"count": 3}

✅ R5 csv+ontology run 5 graded by code

3: E09, E10 and E11.

JSON: {"count": 3}

✅ R4 csv+markdown run 1 graded by code

3: E09, E10, E11.

JSON: {"count": 3}

✅ R4 csv+markdown run 2 graded by code

3: E09, E10 and E11.

JSON: {"count": 3}

✅ R4 csv+markdown run 3 graded by code

3. E09, E10 and E11 (E17 is the same entity as E10).

JSON: {"count": 3}

✅ R4 csv+markdown run 4 graded by code

3. The Halden group is E09, E10 and E11.

JSON: {"count": 3}

✅ R4 csv+markdown run 5 graded by code

Three: E09, E10, E11. E17 is the same entity as E10 by LEI, so it adds no extra count.

JSON: {"count": 3}

✅ R3 csv+padding run 1 graded by code

3 (E09, E10, E11). E17 duplicates E10's LEI.

JSON: {"count": 3}

✅ R3 csv+padding run 2 graded by code

3. The group is E09, E10 and E11. The E17 record is a duplicate of E10.

JSON: {"count": 3}

✅ R3 csv+padding run 3 graded by code

3. The group is E09, E10 and E11. E17 is a duplicate of E10.

JSON: {"count": 3}

✅ R3 csv+padding run 4 graded by code

3 (E09, E10, E11). E17 has the same LEI as E10 and is not counted separately.

JSON: {"count": 3}

✅ R3 csv+padding run 5 graded by code

3: E09, E10 and E11. E17 has the same LEI as E10, so it is the same legal entity.

JSON: {"count": 3}

✅ R10 executed run 1 graded by code

3 (E09, E10, E11).

JSON: {"count": 3}

✅ R10 executed run 2 graded by code

3 (E09, E10, E11). E17 is a merged record of E10, not a separate entity.

JSON: {"count": 3}

✅ R10 executed run 3 graded by code

3 (E09, E10, E11).

JSON: {"count": 3}

✅ R10 executed run 4 graded by code

3: E09, E10, E11.

JSON: {"count": 3}

✅ R10 executed run 5 graded by code

3. The Halden group is E09 (parent), E10 and E11. E12 is not linked.

JSON: {"count": 3}

✅ R7 csv+neutral run 1 graded by code

3 (E09, E10, E11).

JSON: {"count": 3}

✅ R7 csv+neutral run 2 graded by code

3: E09, E10, E11.

JSON: {"count": 3}

✅ R7 csv+neutral run 3 graded by code

3 (E09, E10, E11).

JSON: {"count": 3}

✅ R7 csv+neutral run 4 graded by code

3: E09, E10 and E11. E17 is a RESEARCH duplicate of E10.

JSON: {"count": 3}

✅ R7 csv+neutral run 5 graded by code

3: E09, E10 and E11.

JSON: {"count": 3}

✅ R8 csv+axioms run 1 graded by code

3 (E09, E10, E11). E17 is a RESEARCH duplicate of E10, so it isn't counted separately.

JSON: {"count": 3}

✅ R8 csv+axioms run 2 graded by code

3. The Halden group is E09 (parent), E10 and E11; E17 is a duplicate record of E10 (same LEI).

JSON: {"count": 3}

✅ R8 csv+axioms run 3 graded by code

3. E09, E10 (also recorded as E17), and E11 are the distinct legal entities in the Halden group.

JSON: {"count": 3}

✅ R8 csv+axioms run 4 graded by code

3: E09, E10, E11. E17 is a RESEARCH duplicate of E10.

JSON: {"count": 3}

✅ R8 csv+axioms run 5 graded by code

3: E09, E10, E11.

JSON: {"count": 3}

✅ R9 csv+axioms+markdown run 1 graded by code

3. E09, E10 and E11.

JSON: {"count": 3}

✅ R9 csv+axioms+markdown run 2 graded by code

3.
The Halden group is E09 (parent), E10 (with duplicate E17), and E11.

JSON: {"count": 3}

✅ R9 csv+axioms+markdown run 3 graded by code

3: E09, E10 and E11. E17 is the same entity as E10.

JSON: {"count": 3}

✅ R9 csv+axioms+markdown run 4 graded by code

3: E09, E10 and E11. E17 is the same entity as E10.

JSON: {"count": 3}

✅ R9 csv+axioms+markdown run 5 graded by code

Three: E09, E10 and E11. E17 is a duplicate record of E10.

JSON: {"count": 3}