Q42, run 2026-11-04-2028-haiku

← back to the run

In which country is Halden Bank domiciled?

Tests: Local rule: where records disagree on country, the RESEARCH record holds.

Expected: country = LU

❌ R1 csv run 1 graded by code

DE. E10 (Halden Bank AG) is domiciled in DE. E17, which shares its LEI, lists LU, which conflicts.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R1 csv run 2 graded by code

DE, per E10. E17 gives LU for the same LEI, so the record conflicts.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R1 csv run 3 graded by code

DE. E10 is domiciled in DE, but its duplicate record E17 says LU, so the data conflicts.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R1 csv run 4 graded by code

DE. E10 is domiciled in DE, but E17 with the same LEI lists LU, which is a conflict in the data.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R1 csv run 5 graded by code

DE. E10 is DE, but its duplicate E17 (same LEI) records LU, so the country is contested.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

✅ R5 csv+ontology run 1 graded by code

LU
Domicile follows the RESEARCH record (E17), which says LU, over RATINGS (E10), which says DE.

JSON: {"country": "LU"}

✅ R5 csv+ontology run 2 graded by code

LU. The RESEARCH record E17 gives LU, and for domicile the RESEARCH record holds over RATINGS (E10 says DE).

JSON: {"country": "LU"}

✅ R5 csv+ontology run 3 graded by code

LU. E10 has DE in RATINGS, but E17 (RESEARCH) has LU, and RESEARCH holds for domicile.

JSON: {"country": "LU"}

✅ R5 csv+ontology run 4 graded by code

LU. RESEARCH (E17) holds for domicile and records LU, overriding RATINGS' DE for E10.

JSON: {"country": "LU"}

✅ R5 csv+ontology run 5 graded by code

LU. The RESEARCH record (E17) holds for domicile, so Halden Bank is domiciled in Luxembourg.

JSON: {"country": "LU"}

✅ R4 csv+markdown run 1 graded by code

LU. RATINGS gives DE (E10), but RESEARCH holds for domicile and gives LU (E17).

JSON: {"country": "LU"}

✅ R4 csv+markdown run 2 graded by code

LU. The RESEARCH record (E17) holds for domicile, and it says LU rather than the RATINGS value DE.

JSON: {"country": "LU"}

✅ R4 csv+markdown run 3 graded by code

LU. The RESEARCH record (E17) holds for domicile, and it says LU. The RATINGS record (E10) says DE.

JSON: {"country": "LU"}

✅ R4 csv+markdown run 4 graded by code

LU. RESEARCH holds for domicile, and E17 records LU while E10 records DE.

JSON: {"country": "LU"}

✅ R4 csv+markdown run 5 graded by code

LU. The RESEARCH record (E17) holds for country, and it says LU rather than DE (E10).

JSON: {"country": "LU"}

✅ R8 csv+axioms run 1 graded by code

LU. The RESEARCH record E17 gives Luxembourg, and E10 inherits it through sameEntityAs, although its RATINGS record says DE.

JSON: {"country": "LU"}

✅ R8 csv+axioms run 2 graded by code

LU. The RESEARCH record (E17) gives Luxembourg, and that domicile is applied to the same entity as E10.

JSON: {"country": "LU"}

✅ R8 csv+axioms run 3 graded by code

LU. E17 (RESEARCH) gives LU, and E10 takes that domicile through the shared LEI, even though E10 is registered in DE.

JSON: {"country": "LU"}

✅ R8 csv+axioms run 4 graded by code

LU. E10 is domiciled in LU through its same-entity RESEARCH record E17, even though E10's own country field says DE.

JSON: {"country": "LU"}

✅ R8 csv+axioms run 5 graded by code

LU. Halden Bank's domicile rule uses the RESEARCH record E17, whose country is LU, rather than the RATINGS record E10, whose country is DE.

JSON: {"country": "LU"}