Q42, run 2026-11-05-1227-sonnet

← 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. The RATINGS record E10 says DE; the RESEARCH duplicate E17 says LU, which conflicts, and I treated the RATINGS record as authoritative.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R1 csv run 2 graded by code

DE, per E10 from the RATINGS source. The RESEARCH duplicate E17 says LU, so the data conflicts, and I chose the RATINGS record.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R1 csv run 3 graded by code

DE. The RATINGS record E10 says DE and the RESEARCH duplicate E17 says LU. I took the RATINGS record, but the sources conflict.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R1 csv run 4 graded by code

DE. The RATINGS record E10 says DE, while the RESEARCH duplicate E17 says LU, so the sources conflict and I took the primary record.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R1 csv run 5 graded by code

DE. The RATINGS record E10 says DE, while the RESEARCH duplicate E17 says LU. The conflict is unresolved, and I used the primary source.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R2 rdf run 1 graded by code

DE (E10). The duplicate record E17 says LU, but E10 comes from the RATINGS system.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R2 rdf run 2 graded by code

DE, per E10, which is in the RATINGS source. The duplicate record E17 says LU, so the data conflicts.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R2 rdf run 3 graded by code

DE (E10). The duplicate record E17 says LU.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R2 rdf run 4 graded by code

DE (E10). The duplicate record E17 says LU, so the data conflicts.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R2 rdf run 5 graded by code

DE (E10). The duplicate record E17 says LU, so the data conflicts. I used the RATINGS-system record.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

✅ R6 rdf+ontology run 1 graded by code

LU. The RESEARCH record E17 (LU) overrides E10's DE for domicile.

JSON: {"country": "LU"}

✅ R6 rdf+ontology run 2 graded by code

LU. E17 (RESEARCH) holds for domicile and says LU, over E10's DE.

JSON: {"country": "LU"}

✅ R6 rdf+ontology run 3 graded by code

LU. E17 (RESEARCH) holds for domicile and shares its LEI with E10.

JSON: {"country": "LU"}

✅ R6 rdf+ontology run 4 graded by code

LU. RESEARCH holds on domicile, and E17 says LU while E10 says DE.

JSON: {"country": "LU"}

✅ R6 rdf+ontology run 5 graded by code

LU. The RESEARCH record (E17) holds for domicile, overriding E10's DE.

JSON: {"country": "LU"}

✅ R5 csv+ontology run 1 graded by code

LU. The RESEARCH record (E17) holds for domicile.

JSON: {"country": "LU"}

✅ R5 csv+ontology run 2 graded by code

LU. RESEARCH holds for domicile, so E17's LU overrides E10's DE.

JSON: {"country": "LU"}

✅ R5 csv+ontology run 3 graded by code

LU. RESEARCH holds for domicile (E17).

JSON: {"country": "LU"}

✅ R5 csv+ontology run 4 graded by code

LU. RESEARCH holds on domicile, and E17 says LU.

JSON: {"country": "LU"}

✅ R5 csv+ontology run 5 graded by code

LU. The RESEARCH record E17 holds for domicile.

JSON: {"country": "LU"}

✅ R4 csv+markdown run 1 graded by code

LU. The RESEARCH record E17 holds for country.

JSON: {"country": "LU"}

✅ R4 csv+markdown run 2 graded by code

LU. RESEARCH's record (E17) holds for domicile, and it shares E10's LEI.

JSON: {"country": "LU"}

✅ R4 csv+markdown run 3 graded by code

LU. RESEARCH holds on domicile (E17), overriding the DE in E10.

JSON: {"country": "LU"}

✅ R4 csv+markdown run 4 graded by code

LU. The RESEARCH record E17 holds on domicile.

JSON: {"country": "LU"}

✅ R4 csv+markdown run 5 graded by code

LU. The RESEARCH record (E17) holds for domicile, overriding DE on E10.

JSON: {"country": "LU"}

❌ R3 csv+padding run 1 graded by code

DE. The RATINGS record E10 says DE; E17 (RESEARCH) says LU but is a duplicate of E10 with the same LEI.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R3 csv+padding run 2 graded by code

DE. The RATINGS-system record E10 says DE, and E17 (LU, RESEARCH) is a duplicate by LEI.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R3 csv+padding run 3 graded by code

DE. The RATINGS record E10 says DE, while the RESEARCH duplicate E17 says LU. I treated the RATINGS record as authoritative, which is a judgement call.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R3 csv+padding run 4 graded by code

DE. E10 in the RATINGS system says DE. The RESEARCH duplicate E17 says LU, which conflicts, so I treated it as a data-quality error.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R3 csv+padding run 5 graded by code

DE (E10, from the RATINGS source). The LU on E17 comes from a RESEARCH duplicate record.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

✅ R10 executed run 1 graded by code

Luxembourg (LU), per E10.

JSON: {"country": "LU"}

✅ R10 executed run 2 graded by code

LU (E10).

JSON: {"country": "LU"}

✅ R10 executed run 3 graded by code

Luxembourg (LU), per E10.

JSON: {"country": "LU"}

✅ R10 executed run 4 graded by code

LU (E10).

JSON: {"country": "LU"}

✅ R10 executed run 5 graded by code

LU (E10).

JSON: {"country": "LU"}

✅ R7 csv+neutral run 1 graded by code

LU. The RESEARCH record (E17) holds on domicile, overriding E10's DE.

JSON: {"country": "LU"}

✅ R7 csv+neutral run 2 graded by code

LU. The RESEARCH record (E17) holds for domicile.

JSON: {"country": "LU"}

✅ R7 csv+neutral run 3 graded by code

LU. RESEARCH holds on domicile, and E17 says LU.

JSON: {"country": "LU"}

✅ R7 csv+neutral run 4 graded by code

LU. For domicile the RESEARCH record (E17) holds over the RATINGS record.

JSON: {"country": "LU"}

✅ R7 csv+neutral run 5 graded by code

LU. The RESEARCH record E17 holds for domicile, and it overrides E10's DE.

JSON: {"country": "LU"}

✅ R8 csv+axioms run 1 graded by code

LU. The RESEARCH record E17 gives LU, and it is the same entity as E10.

JSON: {"country": "LU"}

✅ R8 csv+axioms run 2 graded by code

LU. The RESEARCH record E17 for the same LEI gives LU and overrides the RATINGS record's DE.

JSON: {"country": "LU"}

✅ R8 csv+axioms run 3 graded by code

LU. The RESEARCH record E17 gives the country, and E17 is the same entity as E10.

JSON: {"country": "LU"}

✅ R8 csv+axioms run 4 graded by code

LU. The RESEARCH record E17 (the same entity as E10) overrides the DE country on the RATINGS record.

JSON: {"country": "LU"}

✅ R8 csv+axioms run 5 graded by code

LU. The RESEARCH record E17 gives LU, and it overrides E10's DE.

JSON: {"country": "LU"}

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

LU. The RESEARCH record E17 holds for domicile, and E10 has the same LEI.

JSON: {"country": "LU"}

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

LU. The RESEARCH record E17 holds for country and overrides the DE on E10.

JSON: {"country": "LU"}

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

LU. The RESEARCH record E17 holds for country and overrides DE.

JSON: {"country": "LU"}

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

LU. The RESEARCH record E17 holds for country and says LU, though E10 says DE.

JSON: {"country": "LU"}

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

LU. The RESEARCH record E17 holds for country, and it is the same entity as E10.

JSON: {"country": "LU"}