Q42, run 2026-11-05-1233-haiku
In which country is Halden Bank domiciled?
Tests: Local rule: where records disagree on country, the RESEARCH record holds.
Expected: country = LU
csv run 1
DE. E10 (Halden Bank AG) is domiciled in DE, but the RESEARCH record E17 with the same LEI lists LU.
JSON: {"country": "DE"}
Why: country: expected LU, got DE
csv run 2
DE. E10 says Germany, but E17 (same LEI) says LU, so the data conflicts.
JSON: {"country": "DE"}
Why: country: expected LU, got DE
csv run 3
DE. E10's record says DE. E17, which has the same LEI, says LU, so the data conflicts.
JSON: {"country": "DE"}
Why: country: expected LU, got DE
csv run 4
DE. E10 (Halden Bank AG) is DE, but E17 ("HALDEN BANK") with the same LEI is LU, so the data conflicts.
JSON: {"country": "DE"}
Why: country: expected LU, got DE
csv run 5
Unresolved. E10 (RATINGS) gives DE, while E17 (RESEARCH, same LEI) gives LU.
JSON: {"country": "DE or LU (unresolved)"}
Why: country: expected LU, got DE or LU (unresolved)
rdf run 1
DE. Halden Bank AG (E10) is domiciled in Germany. The other "Halden Bank" (E17) is listed as LU, which conflicts with this (see Q15).
JSON: {"country": "DE"}
Why: country: expected LU, got DE
rdf run 2
DE, per E10 (Halden Bank AG). E17, which has the same LEI, is listed as LU, so the data conflicts.
JSON: {"country": "DE"}
Why: country: expected LU, got DE
rdf run 3
DE
Halden Bank AG (E10) is domiciled in Germany. A separate record, E17 "HALDEN BANK", is in LU and shares the same LEI, so the data is conflicting.
JSON: {"country": "DE"}
Why: country: expected LU, got DE
rdf run 4
DE. "Halden Bank" is ambiguous: E10 (Halden Bank AG) is DE, and E17 (HALDEN BANK) is LU. I took E10, the rated entity.
JSON: {"country": "DE"}
Why: country: expected LU, got DE
rdf run 5
Ambiguous. E10 "Halden Bank AG" is DE (RATINGS), while E17 "HALDEN BANK" is LU (RESEARCH); both share LEI 391200QYPVFF2O9K2039.
JSON: {"country": "ambiguous (DE or LU)"}
Why: country: expected LU, got ambiguous (DE or LU)
rdf+ontology run 1
LU. The RESEARCH record (E17) holds for domicile, overriding the RATINGS record (E10: DE).
JSON: {"country": "LU"}
rdf+ontology run 2
LU
The RESEARCH record (E17) overrides E10's DE domicile.
JSON: {"country": "LU"}
rdf+ontology run 3
LU. E10 (Halden Bank AG) records DE in RATINGS, but E17 with the same LEI records LU in RESEARCH, and RESEARCH holds for domicile.
JSON: {"country": "LU"}
rdf+ontology run 4
**LU (Luxembourg).** Where the records disagree on domicile, the RESEARCH record (E17, LU) holds over RATINGS (E10, DE).
JSON: {"country": "LU"}
rdf+ontology run 5
LU
RESEARCH holds for domicile, and E17 (RESEARCH) gives LU, overriding E10's DE.
JSON: {"country": "LU"}
csv+ontology run 1
LU. The RESEARCH record E17 gives LU, and for domicile the RESEARCH record holds over RATINGS' DE.
JSON: {"country": "LU"}
csv+ontology run 2
LU. The RESEARCH record E17 says LU and holds for domicile, overriding E10's DE.
JSON: {"country": "LU"}
csv+ontology run 3
LU. The RESEARCH record (E17) holds for domicile, and it says LU, not DE.
JSON: {"country": "LU"}
csv+ontology run 4
LU. The RESEARCH record (E17) holds for domicile, overriding E10's DE.
JSON: {"country": "LU"}
csv+ontology run 5
LU. The RESEARCH record (E17) holds for domicile over E10's DE.
JSON: {"country": "LU"}
csv+markdown run 1
LU. The RESEARCH record (E17) holds for domicile, and it says LU, not DE.
JSON: {"country": "LU"}
csv+markdown run 2
LU. The RESEARCH record (E17) holds for domicile over the RATINGS record's DE (E10).
JSON: {"country": "LU"}
csv+markdown run 3
LU. RESEARCH (E17) holds for domicile, so Halden Bank is in Luxembourg, not Germany.
JSON: {"country": "LU"}
csv+markdown run 4
LU. For domicile, RESEARCH (E17) holds over RATINGS (E10).
JSON: {"country": "LU"}
csv+markdown run 5
LU. RESEARCH (E17) holds for domicile, and it records LU, not DE.
JSON: {"country": "LU"}
csv+padding run 1
DE, per the rated record E10. E17 records LU, which conflicts with E10.
JSON: {"country": "DE"}
Why: country: expected LU, got DE
csv+padding run 2
DE (E10, Halden Bank AG). E17 lists LU for the same LEI, so the data conflicts.
JSON: {"country": "DE"}
Why: country: expected LU, got DE
csv+padding run 3
DE. The ratings record E10 is domiciled in DE, but E17 (same LEI) says LU. The data conflicts, so DE is the ratings-based answer.
JSON: {"country": "DE"}
Why: country: expected LU, got DE
csv+padding run 4
DE, per E10 (Halden Bank AG). E17 records the same name as LU, but its LEI matches E10.
JSON: {"country": "DE"}
Why: country: expected LU, got DE
csv+padding run 5
DE, per the rated record E10. E17 (same LEI) says LU, so the data conflicts.
JSON: {"country": "DE"}
Why: country: expected LU, got DE
executed run 1
LU. Halden Bank (E10) is domiciled in Luxembourg.
JSON: {"country": "LU"}
executed run 2
LU. Halden Bank (E10) is domiciled in Luxembourg.
JSON: {"country": "LU"}
executed run 3
LU. E10's country is LU.
JSON: {"country": "LU"}
executed run 4
LU (Luxembourg). E10's country is LU.
JSON: {"country": "LU"}
executed run 5
Luxembourg (LU), per entities.csv (E10).
JSON: {"country": "LU"}
csv+neutral run 1
LU. The RESEARCH record (E17) holds for domicile, and it gives Luxembourg, not Germany (E10).
JSON: {"country": "LU"}
csv+neutral run 2
LU. The RESEARCH record E17 holds for domicile, and it records LU (RATINGS says DE).
JSON: {"country": "LU"}
csv+neutral run 3
LU. The RESEARCH record (E17) holds for domicile and overrides the RATINGS record's DE.
JSON: {"country": "LU"}
csv+neutral run 4
LU
RESEARCH holds on domicile, and E17 records LU where RATINGS records DE.
JSON: {"country": "LU"}
csv+neutral run 5
LU. The RESEARCH record (E17) holds for domicile and says LU.
JSON: {"country": "LU"}
csv+axioms run 1
LU. Halden Bank's domicile resolves to Luxembourg via its RESEARCH record (E17, same LEI), which overrides the RATINGS country DE.
JSON: {"country": "LU"}
csv+axioms run 2
LU. Halden Bank's domicile comes from the RESEARCH record E17 (LU), even though the RATINGS record says DE.
JSON: {"country": "LU"}
csv+axioms run 3
LU. E10's RATINGS record says DE, but its same-LEI RESEARCH record E17 says LU, and the domicile rule takes the RESEARCH country.
JSON: {"country": "LU"}
csv+axioms run 4
LU. Halden Bank's RESEARCH record E17 (same entity) gives its country as LU, so the domicile rule assigns LU.
JSON: {"country": "LU"}
csv+axioms run 5
LU
E10's domicile is taken from its RESEARCH duplicate E17, which is domiciled in LU, although E10's own record gives DE.
JSON: {"country": "LU"}
csv+axioms+markdown run 1
LU. The RESEARCH record (E17) holds for domicile and gives Luxembourg, which overrides E10's DE.
JSON: {"country": "LU"}
csv+axioms+markdown run 2
LU. The RESEARCH record (E17) holds for domicile, overriding the RATINGS record's DE.
JSON: {"country": "LU"}
csv+axioms+markdown run 3
LU. The RESEARCH record (E17) holds for domicile.
JSON: {"country": "LU"}
csv+axioms+markdown run 4
LU. E17 is the RESEARCH record, and RESEARCH holds for domicile, so it overrides E10's DE.
JSON: {"country": "LU"}
csv+axioms+markdown run 5
LU. The RESEARCH record E17 holds for domicile, and it gives LU, not DE from E10.
JSON: {"country": "LU"}