Q15, run 2026-11-05-2135-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-. A26 (2023-05-01) set A- and the downgrade A27 is dated 2026-04-15. E17 is a duplicate record of E10.

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

✅ R1 csv run 2 graded by code

A-. E10 had A- from A26 until A27 (2026-04-15). E17 is a duplicate of E10 and has no actions.

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

✅ R1 csv run 3 graded by code

A-. E10 (E17 is a duplicate) was assigned A- in A26, and the downgrade A27 came only on 2026-04-15.

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

✅ R1 csv run 4 graded by code

A-. A26 assigned A- in 2023, and the downgrade to BBB+ (A27) came on 2026-04-15. E17 is a duplicate record of E10.

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

✅ R1 csv run 5 graded by code

A-. E10 was assigned A- (A26) and downgraded to BBB+ only on 2026-04-15 (A27). E17 is a duplicate record of E10.

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

✅ R2 rdf run 1 graded by code

A-. E10 was rated A- from A28/A26's era (2023) until A27 downgraded it to BBB+ on 2026-04-15. The LU record E17 is a research duplicate of E10.

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

✅ R2 rdf run 2 graded by code

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

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

✅ R2 rdf run 3 graded by code

A-. E17 is a duplicate record of E10, and A26 (A-) was in force until the downgrade in A27 on 2026-04-15.

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

✅ R2 rdf run 4 graded by code

A-. E10 was A- (A26) until the A27 downgrade on 2026-04-15; E17 is a duplicate record with the same LEI.

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

✅ R2 rdf run 5 graded by code

A- (A26). The downgrade to BBB+ (A27) is dated 2026-04-15. E17 is a duplicate record for the same entity.

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

✅ R6 rdf+ontology run 1 graded by code

A-. E10 held A- (A26) until the downgrade on 2026-04-15 (A27). E17 is the same entity by LEI.

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

✅ R6 rdf+ontology run 2 graded by code

A-. E10's A- (A26) held until the downgrade in A27 on 2026-04-15. E17 is the same entity (same LEI).

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

✅ R6 rdf+ontology run 3 graded by code

A-. E10 was assigned A- in A26 and was not downgraded until A27 on 2026-04-15. E17 is the same entity and has no actions.

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

✅ R6 rdf+ontology run 4 graded by code

A-. E10 was A- from A26, and the downgrade (A27) only came on 2026-04-15.

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

✅ R6 rdf+ontology run 5 graded by code

A-. E10 was assigned A- on 2023-05-01 (A26) and downgraded to BBB+ on 2026-04-15 (A27).

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

✅ R5 csv+ontology run 1 graded by code

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

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

✅ R5 csv+ontology run 2 graded by code

A-. The downgrade to BBB+ (A27) came on 2026-04-15, after that date.

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

✅ R5 csv+ontology run 3 graded by code

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

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

✅ R5 csv+ontology run 4 graded by code

A-. E10 and E17 share an LEI, and A26 (A-) held until A27 (2026-04-15).

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

✅ R5 csv+ontology run 5 graded by code

A-. A26 assigned it to E10; the downgrade A27 came on 2026-04-15.

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

✅ R4 csv+markdown run 1 graded by code

A-. E10 and E17 are one entity, and A26 holds until the downgrade on 2026-04-15 (A27).

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

✅ R4 csv+markdown run 2 graded by code

A-. E10 and E17 share an LEI, and A26 (A-) was the latest action before A27 on 2026-04-15.

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

✅ R4 csv+markdown run 3 graded by code

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

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

✅ R4 csv+markdown run 4 graded by code

A-. E10's A26 holds until A27 on 2026-04-15, and E17 is just the research duplicate of E10.

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

✅ R4 csv+markdown run 5 graded by code

A-. E10 and E17 share an LEI, so they are one entity, and its downgrade to BBB+ (A27) came on 2026-04-15.

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

✅ R3 csv+padding run 1 graded by code

A-. A26 (E10, 2023) set A-, and the downgrade A27 came on 2026-04-15. E17 is a duplicate record with no actions.

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

✅ R3 csv+padding run 2 graded by code

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

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

✅ R3 csv+padding run 3 graded by code

A-. A26 assigned it in 2023, and the downgrade A27 came on 2026-04-15.

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

✅ R3 csv+padding run 4 graded by code

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

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

✅ R3 csv+padding run 5 graded by code

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

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

✅ R10 executed run 1 graded by code

A-. E10 held A- until 2026-04-15 (A26).

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

✅ R10 executed run 2 graded by code

A-. A26 runs from 2023-05-01 to 2026-04-15.

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

✅ R10 executed run 3 graded by code

A- until 2026-04-15, when it moved to BBB+ (A26/A27).

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

✅ R10 executed run 4 graded by code

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

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

✅ R10 executed run 5 graded by code

A-. E10 was A- until 2026-04-15 (A26).

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

✅ R7 csv+neutral run 1 graded by code

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

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

✅ R7 csv+neutral run 2 graded by code

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

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

✅ R7 csv+neutral run 3 graded by code

A-. E10 and E17 share a LEI, and the downgrade A27 only came on 2026-04-15.

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

✅ R7 csv+neutral run 4 graded by code

A-. E10's downgrade to BBB+ (A27) is dated 2026-04-15, after the date asked.

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

✅ R7 csv+neutral run 5 graded by code

A-. A26 set A- for E10 (E17 is the same entity), and the downgrade A27 came on 2026-04-15.

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

✅ R8 csv+axioms run 1 graded by code

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

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

✅ R8 csv+axioms run 2 graded by code

A-. A26 assigned it in 2023, and the downgrade (A27) came on 2026-04-15. E17 is just the research record for the same LEI.

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

✅ R8 csv+axioms run 3 graded by code

A-. E17 shares E10's LEI, and E10 was rated A- from 2023-05-01 (A26). It was downgraded to BBB+ only on 2026-04-15 (A27).

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

✅ R8 csv+axioms run 4 graded by code

A-. E17 is the same entity as E10, which held A- from A26 (2023) until A27 (2026-04-15).

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

✅ R8 csv+axioms run 5 graded by code

A-. E10 and E17 share an LEI, and the A- from A26 stood until the 2026-04-15 downgrade (A27).

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

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

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

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

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

A-. E10 and E17 are the same entity, and the A- from A26 held until the downgrade on 2026-04-15.

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

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

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

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

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

A-. A26 set E10 at A- in 2023, and the downgrade (A27) is not until 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 downgraded on 2026-04-15 (A27).

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