Q42, run 2026-11-05-2135-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. E10 (RATINGS source) says DE, while its duplicate E17 (RESEARCH) says LU, so the data conflicts.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R1 csv run 2 graded by code

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

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R1 csv run 3 graded by code

DE (E10, RATINGS source). The research duplicate E17 says LU.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R1 csv run 4 graded by code

DE. E10 in the RATINGS source says DE; the RESEARCH duplicate E17 says LU.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R1 csv run 5 graded by code

DE. The RATINGS record E10 says DE. The RESEARCH duplicate E17 says LU, which conflicts.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R2 rdf run 1 graded by code

DE (E10, RATINGS system). The research duplicate E17 says LU, so the sources conflict.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R2 rdf run 2 graded by code

DE (E10). The duplicate record E17 says LU, with the same LEI.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R2 rdf run 3 graded by code

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

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R2 rdf run 4 graded by code

DE. E10 says DE, but the duplicate research record E17 says LU, so the data conflicts and I used the RATINGS record.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R2 rdf run 5 graded by code

DE (E10). The duplicate record E17 (same LEI) says LU, so there is a conflict. I used the RATINGS record.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

✅ R6 rdf+ontology run 1 graded by code

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

JSON: {"country": "LU"}

✅ R6 rdf+ontology run 2 graded by code

LU. RESEARCH holds for domicile, and its record E17 says LU, whereas the RATINGS record E10 says DE.

JSON: {"country": "LU"}

✅ R6 rdf+ontology run 3 graded by code

LU. E10 says DE, but the RESEARCH record E17 holds for domicile and says LU.

JSON: {"country": "LU"}

✅ R6 rdf+ontology run 4 graded by code

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

JSON: {"country": "LU"}

✅ R6 rdf+ontology run 5 graded by code

LU. E17 is the RESEARCH record of E10, and the RESEARCH record holds for country.

JSON: {"country": "LU"}

✅ R5 csv+ontology run 1 graded by code

LU. The RESEARCH record E17 holds for domicile and says LU, overriding the RATINGS record's DE.

JSON: {"country": "LU"}

✅ R5 csv+ontology run 2 graded by code

LU. The RESEARCH record E17 holds for domicile, so E10 is domiciled in Luxembourg rather than DE.

JSON: {"country": "LU"}

✅ R5 csv+ontology run 3 graded by code

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

JSON: {"country": "LU"}

✅ R5 csv+ontology run 4 graded by code

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

JSON: {"country": "LU"}

✅ R5 csv+ontology run 5 graded by code

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

JSON: {"country": "LU"}

✅ R4 csv+markdown run 1 graded by code

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

JSON: {"country": "LU"}

✅ R4 csv+markdown run 2 graded by code

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

JSON: {"country": "LU"}

✅ R4 csv+markdown run 3 graded by code

LU. The RESEARCH record E17 holds for domicile, and it says LU, not DE.

JSON: {"country": "LU"}

✅ R4 csv+markdown run 4 graded by code

LU. The RESEARCH record E17 holds for domicile, and it says LU while E10 says DE.

JSON: {"country": "LU"}

✅ R4 csv+markdown run 5 graded by code

LU. The RESEARCH record E17 overrides E10's DE.

JSON: {"country": "LU"}

❌ R3 csv+padding run 1 graded by code

DE (E10). E17 is a RESEARCH duplicate (same LEI) that conflicts by showing LU.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R3 csv+padding run 2 graded by code

DE. E10 (RATINGS source) says DE, while the duplicate E17 (RESEARCH source) says LU; I used the RATINGS record.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R3 csv+padding run 3 graded by code

DE. E10 says DE and the RESEARCH duplicate E17 says LU, so I took the RATINGS record.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R3 csv+padding run 4 graded by code

DE. E10 is DE; E17 is a RESEARCH duplicate with the same LEI that lists LU.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

❌ R3 csv+padding run 5 graded by code

DE. RATINGS says DE for E10, while the duplicate research record E17 says LU, which conflicts; I used the RATINGS source.

JSON: {"country": "DE"}

Why: country: expected LU, got DE

✅ R10 executed run 1 graded by code

LU. This is E10's country in entities.csv.

JSON: {"country": "LU"}

✅ R10 executed run 2 graded by code

LU (E10).

JSON: {"country": "LU"}

✅ R10 executed run 3 graded by code

LU (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. RATINGS says DE, but RESEARCH (E17) holds for domicile and says LU.

JSON: {"country": "LU"}

✅ R7 csv+neutral run 2 graded by code

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

JSON: {"country": "LU"}

✅ R7 csv+neutral run 3 graded by code

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

JSON: {"country": "LU"}

✅ R7 csv+neutral run 4 graded by code

LU. The RESEARCH record E17 holds on domicile.

JSON: {"country": "LU"}

✅ R7 csv+neutral run 5 graded by code

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

JSON: {"country": "LU"}

✅ R8 csv+axioms run 1 graded by code

LU. The research record E17 shares E10's LEI and gives LU.

JSON: {"country": "LU"}

✅ R8 csv+axioms run 2 graded by code

LU. The RESEARCH record E17 (LU) takes precedence over the RATINGS record E10 (DE).

JSON: {"country": "LU"}

✅ R8 csv+axioms run 3 graded by code

LU. The RESEARCH record E17 gives LU for the same LEI as E10, and research country takes precedence.

JSON: {"country": "LU"}

✅ R8 csv+axioms run 4 graded by code

LU. Domicile follows the RESEARCH record (E17, LU), while E10's RATINGS record says DE; the data conflicts.

JSON: {"country": "LU"}

✅ R8 csv+axioms run 5 graded by code

LU. The RESEARCH record E17 gives LU, which overrides the RATINGS record's DE under the domicile rule.

JSON: {"country": "LU"}

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

LU. The RESEARCH record E17 holds domicile for the entity it shares with E10.

JSON: {"country": "LU"}

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

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

JSON: {"country": "LU"}

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

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

JSON: {"country": "LU"}

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

LU. The RESEARCH record E17 holds for domicile, overriding the RATINGS record's DE.

JSON: {"country": "LU"}

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

LU. The RESEARCH record E17 holds for domicile, and E10 and E17 share an LEI.

JSON: {"country": "LU"}