Q15, run 2026-11-05-1227-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 A26 set A- until A27 on 2026-04-15.

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

✅ R1 csv run 2 graded by code

A-. E17 shares E10's LEI, so it is the same entity, and the downgrade to BBB+ (A27) came only on 2026-04-15.

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

✅ R1 csv run 3 graded by code

A-. E17 shares E10's LEI, so it is the same entity, and E10 was rated A- (A26) until 2026-04-15 (A27).

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

✅ R1 csv run 4 graded by code

A-. A26 assigned it to E10 and A27 only downgraded it on 2026-04-15. E17 is the same entity as E10 (same LEI).

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

✅ R1 csv run 5 graded by code

A-. E10 was assigned A- by A26; the downgrade to BBB+ (A27) came in April 2026. E17 is the same LEI.

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

✅ R2 rdf run 1 graded by code

A-. E10 was rated A- (A26) until the downgrade on 2026-04-15 (A27). E17 shares E10's LEI and has no ratings.

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

✅ R2 rdf run 2 graded by code

A-. E10 and E17 share an LEI, so they are the same entity. A26 gave A- and the downgrade A27 came on 2026-04-15.

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

✅ R2 rdf run 3 graded by code

A-. E10 was assigned A- in 2023 (A26) and not downgraded until 2026-04-15 (A27). E17 has the same LEI and no ratings.

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

✅ R2 rdf run 4 graded by code

A-. E10 was assigned A- in A26 and not downgraded until A27 (2026-04-15). E17 is a same-LEI duplicate with no ratings.

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

✅ R2 rdf run 5 graded by code

A-. E10 was rated A- from A26 until the downgrade in A27 (2026-04-15). E17 shares E10's LEI and has no ratings.

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

✅ R6 rdf+ontology run 1 graded by code

A-. The Halden Bank record E17 has no actions, and E10 (same LEI) held A- (A26) until A27 on 2026-04-15.

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

✅ R6 rdf+ontology run 2 graded by code

A-. E10 (also recorded as E17) was assigned A- on 2023-05-01 (A26) and downgraded on 2026-04-15 (A27).

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

✅ R6 rdf+ontology run 3 graded by code

A-. E10/E17 held A- (A26) until the downgrade A27 on 2026-04-15.

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

✅ R6 rdf+ontology run 4 graded by code

A-. E17 and E10 share an LEI. E10 was assigned A- (A26) and not downgraded until 2026-04-15 (A27).

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

✅ R6 rdf+ontology run 5 graded by code

A-. E10 (the same entity as E17) 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-. A26 assigned A- to E10, which is the same entity as E17. The downgrade to BBB+ (A27) came on 2026-04-15.

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

✅ R5 csv+ontology run 2 graded by code

A-. A26 set A- for E10 in 2023, and the downgrade A27 came only on 2026-04-15.

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

✅ R5 csv+ontology run 3 graded by code

A-. E10 was assigned A- on 2023-05-01 (A26) and was not downgraded until A27 on 2026-04-15.

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

✅ R5 csv+ontology run 4 graded by code

A-. E17 is the same entity as E10, and the downgrade to BBB+ (A27) came only on 2026-04-15.

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

✅ R5 csv+ontology run 5 graded by code

A-. E10 and E17 are the same entity, and A26 set A-. The downgrade A27 came on 2026-04-15.

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

✅ R4 csv+markdown run 1 graded by code

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

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

✅ R4 csv+markdown run 2 graded by code

A-. A26 applies to E10, which is the same entity as E17, and the downgrade A27 only came in April 2026.

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

✅ R4 csv+markdown run 3 graded by code

A-. E10 was assigned A- (A26), and the downgrade to BBB+ came on 2026-04-15 (A27).

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

✅ R4 csv+markdown run 4 graded by code

A-. E17 is the same entity as E10, and A26 set A- until A27 on 2026-04-15.

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

✅ R4 csv+markdown run 5 graded by code

A-. E17 is the same entity as E10, and A26 holds until the 2026-04-15 downgrade (A27).

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

✅ R3 csv+padding run 1 graded by code

A-. E17 is the same entity as E10 (same LEI), and E10 held A- from A26 until the 2026-04-15 downgrade.

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

✅ R3 csv+padding run 2 graded by code

A-. A26 gave E10 A- in 2023, and E17 is the same LEI. The downgrade A27 came only in April 2026.

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

✅ R3 csv+padding run 3 graded by code

A-. E10 was assigned A- on 2023-05-01 (A26), and the downgrade did not come until 2026-04-15 (A27). E17 is a duplicate of E10.

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

✅ R3 csv+padding run 4 graded by code

A-. E17 is a duplicate of E10, whose A- (A26) stood until the 2026-04-15 downgrade (A27).

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

✅ R3 csv+padding run 5 graded by code

A-. E10's rating was A- from 2023 (A26) until the cut on 2026-04-15 (A27). E17 is a duplicate record.

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

✅ R10 executed run 1 graded by code

A- (A26).

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

✅ R10 executed run 2 graded by code

A- (A26, valid until 2026-04-15).

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

✅ R10 executed run 3 graded by code

A- (A26).

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

✅ R10 executed run 4 graded by code

A- (A26, valid until 2026-04-15).

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

✅ R10 executed run 5 graded by code

A-. This is E10's rating from 2023-05-01 to 2026-04-15 (A26).

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

✅ R7 csv+neutral run 1 graded by code

A-. E10 was assigned A- by A26 and downgraded only on 2026-04-15 (A27).

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

✅ R7 csv+neutral run 2 graded by code

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

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

✅ R7 csv+neutral run 3 graded by code

A-. A26 assigned A- on 2023-05-01, and the downgrade (A27) came on 2026-04-15. E17 is the same entity as E10.

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

✅ R7 csv+neutral run 4 graded by code

A-. E17 is the same entity as E10, and A26 stood until A27 on 2026-04-15.

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

✅ R7 csv+neutral run 5 graded by code

A-. E17 has the same LEI as E10, so they are one entity. A26 gave A-, and the downgrade A27 only came on 2026-04-15.

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

✅ R8 csv+axioms run 1 graded by code

A-. E17 shares E10's LEI, and A26 was in force until A27 on 2026-04-15.

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

✅ R8 csv+axioms run 2 graded by code

A-. A26 was in force until A27 on 2026-04-15, and E17 has no actions of its own.

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

✅ R8 csv+axioms run 3 graded by code

A-. A26 (E10) was in force until A27 on 2026-04-15, and E17 is the same entity.

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

✅ R8 csv+axioms run 4 graded by code

A-. A26 was in force until A27 (2026-04-15). E17 is the same entity as E10.

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

✅ R8 csv+axioms run 5 graded by code

A-. A26 was in force until A27 on 2026-04-15, and E17 has no actions.

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

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

A-. E10 and E17 are the same entity, and A26 is still in force on that date (A27 came in April 2026).

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

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

A-. A26 set A- in 2023 for E10, and the downgrade A27 was not until 2026-04-15.

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

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

A-. E10's A26 holds until A27 on 2026-04-15.

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

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

A-. E10's rating was A- from A26 until the downgrade A27 on 2026-04-15.

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

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

A-. E10 was assigned A- on 2023-05-01 (A26), and the downgrade A27 came on 2026-04-15.

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