Q15, run 2026-11-04-1825-sonnet

← back to the run

What was Halden Bank's rating on 1 January 2026?

Tests: Time: the downgrade came later in 2026.

Expected: rating = A-

✅ R1 csv run 1 graded by code

A-. E17 shares E10's LEI, and E10 was rated A- from 2023-05-01 (A26) until the 2026-04-15 downgrade (A27).

JSON: {"rating": "A-"}

✅ R1 csv run 2 graded by code

A-. E10 was assigned A- in A26. The record E17 shares its LEI. The downgrade to BBB+ (A27) came in April 2026.

JSON: {"rating": "A-"}

✅ R1 csv run 3 graded by code

A-. A26 is the rating on 2026-01-01, and E17 is the same LEI. The downgrade to BBB+ (A27) came on 2026-04-15.

JSON: {"rating": "A-"}

✅ R1 csv run 4 graded by code

A-. A26 assigned it in 2023, and the downgrade to BBB+ (A27) did not come until 2026-04-15. E17 is a duplicate of E10.

JSON: {"rating": "A-"}

✅ R1 csv run 5 graded by code

A-. E10 (E17 has the same LEI) was rated A- from A26 until the downgrade in A27 on 2026-04-15.

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 1 graded by code

A-. E10 and E17 share an LEI, so they are one entity, and A26 (A-) held until the downgrade A27 on 2026-04-15.

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 2 graded by code

A-. E10 was assigned A- in A26, and E17 is the same entity with no further actions before 2026-04-15.

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 3 graded by code

A-. E17 is the same entity as E10, and the A27 downgrade did not happen until 2026-04-15, so A26's A- still held.

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 4 graded by code

A-. E10 was assigned A- in A26, and the downgrade A27 came on 2026-04-15. E17 is the same entity as E10, and the RATINGS record holds.

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 5 graded by code

A-. E10 and E17 are the same entity, and A26 holds until A27 on 2026-04-15.

JSON: {"rating": "A-"}

✅ R8 csv+axioms run 1 graded by code

A-. A26 was in force until the downgrade A27 on 2026-04-15. E17 is the same entity (same LEI) and has no actions of its own.

JSON: {"rating": "A-"}

✅ R8 csv+axioms run 2 graded by code

A-. E10 was assigned A- in A26 and was not downgraded until 2026-04-15 (A27).

JSON: {"rating": "A-"}

✅ R8 csv+axioms run 3 graded by code

A-. A26 assigned A- to E10 in 2023, and the downgrade A27 came on 2026-04-15. E17 is the same entity.

JSON: {"rating": "A-"}

✅ R8 csv+axioms run 4 graded by code

A-. A26 was in force until the 2026-04-15 downgrade (A27).

JSON: {"rating": "A-"}

✅ R8 csv+axioms run 5 graded by code

A-. A26 was in force until A27 on 2026-04-15. E17 shares the LEI of E10, so it is the same entity and has no actions of its own.

JSON: {"rating": "A-"}

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

A-. E10 and E17 are the same entity, and the downgrade A27 only took effect on 2026-04-15.

JSON: {"rating": "A-"}

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

A-. A26 was in force, and the downgrade A27 came on 2026-04-15.

JSON: {"rating": "A-"}

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

A-. E17 has the same LEI as E10, and A26 set A- until the downgrade on 2026-04-15.

JSON: {"rating": "A-"}

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

A-. A26 set it and the downgrade A27 came on 2026-04-15.

JSON: {"rating": "A-"}

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

A-. A26 assigned E10 A- and no later action was recorded against E10 or its duplicate E17 until A27 (2026-04-15), which is after 2026-01-01.

JSON: {"rating": "A-"}