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

← back to the run

In which country is Halden Bank domiciled?

Tests: Local rule: where records disagree, the RATINGS record holds.

Expected: country = DE

✅ R1 csv run 1 graded by code

DE. E10 (Halden Bank AG) is domiciled in DE, but E17 (same LEI) says LU, so the data conflicts.

JSON: {"country": "DE"}

✅ R1 csv run 2 graded by code

DE, per E10 (the rated record). E17 gives LU for the same LEI, so the data conflicts.

JSON: {"country": "DE"}

✅ R1 csv run 3 graded by code

DE. E10 records Germany; E17 (same LEI) says LU. The conflict is not resolved by the data, so I use the RATINGS record.

JSON: {"country": "DE"}

✅ R1 csv run 4 graded by code

DE, per E10 (RATINGS). E17 (RESEARCH, same LEI) lists LU, so the data conflicts and I can't settle which is correct.

JSON: {"country": "DE"}

✅ R1 csv run 5 graded by code

DE. The ratings record (E10) gives DE, but the duplicate research record (E17) gives LU for the same LEI. This conflict is unresolved in the data.

JSON: {"country": "DE"}

✅ R2 rdf run 1 graded by code

DE
E10 (Halden Bank AG) is domiciled in DE. A separate record, E17 "HALDEN BANK", shows LU and shares E10's LEI, so the country conflicts.

JSON: {"country": "DE"}

✅ R2 rdf run 2 graded by code

DE, with a conflict. E10 (Halden Bank AG) says DE, but E17 (HALDEN BANK, same LEI) says LU. The data does not settle which is correct.

JSON: {"country": "DE"}

✅ R2 rdf run 3 graded by code

DE. E10 (Halden Bank AG) is in DE, but E17 (same LEI) says LU, so the data conflicts.

JSON: {"country": "DE"}

✅ R2 rdf run 4 graded by code

DE, per E10 (Halden Bank AG, LEI HLDN00BANK000000DE62). E17 has the same LEI but lists LU, so the records conflict.

JSON: {"country": "DE"}

✅ R2 rdf run 5 graded by code

DE
E10 (Halden Bank AG, RATINGS) says DE, but E17 (HALDEN BANK, RESEARCH, same LEI) says LU. The records conflict.

JSON: {"country": "DE"}

✅ R6 rdf+ontology run 1 graded by code

DE. The RATINGS record (E10) overrides the RESEARCH record (E17, LU) because RATINGS is the system of record.

JSON: {"country": "DE"}

✅ R6 rdf+ontology run 2 graded by code

DE.
The RATINGS record (E10) holds the country as DE, and the RATINGS record wins over the RESEARCH record E17 (LU).

JSON: {"country": "DE"}

✅ R6 rdf+ontology run 3 graded by code

DE. The RATINGS record E10 holds Germany; the RESEARCH record E17 says LU, but RATINGS is the system of record.

JSON: {"country": "DE"}

✅ R6 rdf+ontology run 4 graded by code

DE. RATINGS governs for E10 (Halden Bank AG), and the RESEARCH record's LU is overridden.

JSON: {"country": "DE"}

✅ R6 rdf+ontology run 5 graded by code

DE. The RATINGS record for E10 (Halden Bank AG) holds, which overrides the RESEARCH record E17 that says LU.

JSON: {"country": "DE"}

✅ R5 csv+ontology run 1 graded by code

DE. RATINGS (E10) is the system of record, so E17's LU country is overridden.

JSON: {"country": "DE"}

✅ R5 csv+ontology run 2 graded by code

DE. RATINGS (E10) holds the country, and RESEARCH (E17) says LU, which is overridden.

JSON: {"country": "DE"}

✅ R5 csv+ontology run 3 graded by code

DE. RATINGS is the system of record, and E10 is recorded there as DE. The RESEARCH record E17 says LU, but it is overridden.

JSON: {"country": "DE"}

✅ R5 csv+ontology run 4 graded by code

DE. The RATINGS record (E10) holds, and it gives Germany; the RESEARCH record (E17) gives LU.

JSON: {"country": "DE"}

✅ R5 csv+ontology run 5 graded by code

DE
RATINGS holds for country, and E10 is DE. E17's LU is from RESEARCH, which is not the system of record.

JSON: {"country": "DE"}

✅ R4 csv+markdown run 1 graded by code

DE. The RATINGS record for E10 holds, so the LU domicile in E17 (RESEARCH) is overridden.

JSON: {"country": "DE"}

✅ R4 csv+markdown run 2 graded by code

Germany (DE). RATINGS holds the country for Halden Bank (E10), and the RESEARCH record E17 gives LU.

JSON: {"country": "DE"}

✅ R4 csv+markdown run 3 graded by code

DE. The RATINGS record (E10) holds, over the RESEARCH record's LU (E17).

JSON: {"country": "DE"}

✅ R4 csv+markdown run 4 graded by code

DE. RATINGS (E10) is the system of record, and its country is DE. The RESEARCH record E17 says LU, but RATINGS takes precedence.

JSON: {"country": "DE"}

✅ R4 csv+markdown run 5 graded by code

DE. The RATINGS record E10 holds, and the RESEARCH record's LU is superseded.

JSON: {"country": "DE"}

✅ R3 csv+padding run 1 graded by code

DE, with a conflict. E10 is domiciled in DE, but E17 (same LEI) lists LU. The data does not settle which is correct.

JSON: {"country": "DE"}

✅ R3 csv+padding run 2 graded by code

DE, from E10. E17 gives LU for the same LEI, so the records conflict.

JSON: {"country": "DE"}

✅ R3 csv+padding run 3 graded by code

DE. RATINGS places E10 in DE, but E17 (same LEI, RESEARCH source) says LU, which conflicts with it.

JSON: {"country": "DE"}

✅ R3 csv+padding run 4 graded by code

DE, per E10. E17 (same LEI, RESEARCH source) lists LU, which conflicts with E10.

JSON: {"country": "DE"}

✅ R3 csv+padding run 5 graded by code

DE. E10 (Halden Bank AG) is listed as DE, but E17 gives LU for the same LEI, so the records conflict.

JSON: {"country": "DE"}