Q35, run 2026-11-05-1233-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. The Halden group is E09, E10 and E11. E17 shares E10's LEI, so it is not counted separately.

JSON: {"count": 3}

✅ R1 csv run 2 graded by code

3: E09, E10, and E11. E17 duplicates E10 (same LEI).

JSON: {"count": 3}

✅ R1 csv run 3 graded by code

3. The group is E09 (parent), E10, and E11. E17 has the same LEI as E10, so it is not a separate entity.

JSON: {"count": 3}

✅ R1 csv run 4 graded by code

3: E09, E10, E11. E17 shares E10's LEI, so it is not counted separately.

JSON: {"count": 3}

✅ R1 csv run 5 graded by code

3. E09, E10 and E11 are the Halden group. E17 has the same LEI as E10, so it is the same entity.

JSON: {"count": 3}

✅ R2 rdf run 1 graded by code

3: E09, E10 and E11.

JSON: {"count": 3}

✅ R2 rdf run 2 graded by code

3: E09, E10 and E11. E17 has E10's LEI, so it is not counted separately, and it has no parent link to E09.

JSON: {"count": 3}

✅ R2 rdf run 3 graded by code

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

JSON: {"count": 3}

✅ R2 rdf run 4 graded by code

3. The Halden group is E09 (parent), E10 (parent E09) and E11 (parent E10). E12 and E17 share the name but have no parent link.

JSON: {"count": 3}

✅ R2 rdf run 5 graded by code

3: E09, E10 and E11. E12 has no recorded parent link, and E17 shares E10's LEI so is not added.

JSON: {"count": 3}

✅ R6 rdf+ontology run 1 graded by code

3: E09, E10 (with E17, same LEI) and E11.

JSON: {"count": 3}

✅ R6 rdf+ontology run 2 graded by code

3
These are E09, E10 (including its E17 record) and E11.

JSON: {"count": 3}

✅ R6 rdf+ontology run 3 graded by code

3. The group is E09, E10 and E11, with E17 counted as E10.

JSON: {"count": 3}

✅ R6 rdf+ontology run 4 graded by code

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

JSON: {"count": 3}

✅ R6 rdf+ontology run 5 graded by code

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

JSON: {"count": 3}

✅ R5 csv+ontology run 1 graded by code

3. The Halden group is E09, E10 and E11. E12 has no parent link and is not in the group.

JSON: {"count": 3}

✅ R5 csv+ontology run 2 graded by code

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

JSON: {"count": 3}

✅ R5 csv+ontology run 3 graded by code

3. The Halden group is E09, E10 (also E17) and E11.

JSON: {"count": 3}

✅ R5 csv+ontology run 4 graded by code

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

JSON: {"count": 3}

✅ R5 csv+ontology run 5 graded by code

3. These are E09, E10 and E11.

JSON: {"count": 3}

✅ R4 csv+markdown run 1 graded by code

3. The Halden group is E09, E10 and E11. E17 is a second record for E10.

JSON: {"count": 3}

✅ R4 csv+markdown run 2 graded by code

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

JSON: {"count": 3}

✅ R4 csv+markdown run 3 graded by code

3. The group is E09, E10 (Halden Bank, also recorded as E17) and E11.

JSON: {"count": 3}

✅ R4 csv+markdown run 4 graded by code

3. E09, E10 (also E17) and E11 are in the Halden group.

JSON: {"count": 3}

✅ R4 csv+markdown run 5 graded by code

3. The Halden group is E09, E10 (which includes E17, the same LEI) and E11.

JSON: {"count": 3}

✅ R3 csv+padding run 1 graded by code

3: Halden Group (E09), Halden Bank AG (E10) and Halden Leasing (E11). E17 is a duplicate of E10.

JSON: {"count": 3}

✅ R3 csv+padding run 2 graded by code

3: E09, E10, E11. E17 has E10's LEI and is not counted separately.

JSON: {"count": 3}

✅ R3 csv+padding run 3 graded by code

3. These are E09, E10, and E11. E17 is the same LEI as E10.

JSON: {"count": 3}

✅ R3 csv+padding run 4 graded by code

3: E09, E10 and E11. E17 has the same LEI as E10 but no parent link, so it is excluded.

JSON: {"count": 3}

✅ R3 csv+padding run 5 graded by code

3: E09, E10 and E11. E17 is the same LEI as E10 and so is not a separate entity, and E12 has no link to the group.

JSON: {"count": 3}

✅ R10 executed run 1 graded by code

3. The Halden group is E09 (parent), E10 and E11; E17 was merged into E10 and is not a separate entity.

JSON: {"count": 3}

✅ R10 executed run 2 graded by code

3: E09, E10 and E11. E17 is a record merged into E10, not a separate entity.

JSON: {"count": 3}

✅ R10 executed run 3 graded by code

3. The Halden group is E09, E10 and E11. E17 is a record merged into E10, not a separate entity.

JSON: {"count": 3}

✅ R10 executed run 4 graded by code

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

JSON: {"count": 3}

✅ R10 executed run 5 graded by code

3. The Halden group is E09, E10 and E11; E12 has no parent link, and E17 is merged into E10.

JSON: {"count": 3}

✅ R7 csv+neutral run 1 graded by code

3. The Halden group is E09 (Halden Group plc), E10 (Halden Bank, also recorded as E17) and E11 (Halden Leasing).

JSON: {"count": 3}

✅ R7 csv+neutral run 2 graded by code

3. The Halden group is E09, E10 (including the RESEARCH record E17) and E11.

JSON: {"count": 3}

✅ R7 csv+neutral run 3 graded by code

3. The Halden group is E09 (parent), E10 (Halden Bank, with E17 as its alias) and E11 (Halden Leasing). Halden Foods (E12) is not in it.

JSON: {"count": 3}

✅ R7 csv+neutral run 4 graded by code

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

JSON: {"count": 3}

✅ R7 csv+neutral run 5 graded by code

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

JSON: {"count": 3}

✅ R8 csv+axioms run 1 graded by code

3. The Halden group is E09 (parent), E10 (Halden Bank AG, which also matches E17) and E11.

JSON: {"count": 3}

✅ R8 csv+axioms run 2 graded by code

3. The Halden group is E09, E10, and E11, with E17 being the same legal entity as E10.

JSON: {"count": 3}

✅ R8 csv+axioms run 3 graded by code

3. These are E09, E10 (with E17, the same LEI) and E11.

JSON: {"count": 3}

✅ R8 csv+axioms run 4 graded by code

3. The Halden group is E09, E10 (which includes E17) and E11.

JSON: {"count": 3}

✅ R8 csv+axioms run 5 graded by code

3
The group is E09, E10 (also recorded as E17, same LEI) and E11.

JSON: {"count": 3}

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

3. The Halden group is E09, E10 and E11. E17 is a second record for E10, so it is not counted separately.

JSON: {"count": 3}

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

3. The group is E09, E10 and E11.

JSON: {"count": 3}

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

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

JSON: {"count": 3}

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

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

JSON: {"count": 3}

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

3. The Halden group is E09, E10 and E11. E17 is the same entity as E10, and E12 is not in the group.

JSON: {"count": 3}