Define a deal before counting one
The corpus distinguishes seven events. Preserve the original source wording alongside the normalized classification.
An institution can sign a facility, register security, draw twice, amend the limit and release the security. That sequence can produce many public records but still describe one facility. A syndicated facility can name many lenders without becoming one deal per lender. A single borrower can also have multiple genuinely distinct facilities.
The Canada Infrastructure Bank’s investment process distinguishes its investment stages. Bank Act Security Registry principles also show why a registry release does not automatically prove repayment: release can follow a situation in which no security was given.
Corpus objects
These are research objects, not new public API resources. Preserve the distinction between an issuer and its borrowing subsidiary, and between a lender, an administrative agent and a guarantor.
Construct the corpus
- Acquire a bounded source release. Record query parameters, pagination, coverage dates and returned bytes. Save failures and unavailable fields as part of the acquisition record.
- Assign a source unit. Identify whether each row is a company, registration, signed support transaction, annual aggregate, document, facility or outcome. Reject unitless counts.
- Extract source claims. Retain page and row locations, stated units, dates, amount ranges and conditional language. Keep absent values null.
- Resolve entities conservatively. Prefer registry identifiers. Use name, jurisdiction, address and legal form for candidate generation. Preserve uncertain matches for review; similar names alone do not justify merging.
- Build facility families. Link amendments, renewals and syndicated participants to the original facility when evidence supports the relationship. Keep competing linkage hypotheses when it does not.
- Create the historical view. A record enters the input only when it was publicly available by the assessment cutoff. Signing date alone does not establish publication availability.
- Qualify task labels. A disclosed amount can label extraction. A matched registration can label a security relationship. Neither automatically labels repayment, affordability or fraud.
- Freeze the release. Publish aggregate counts, exclusion reasons, schema and hashes. Keep restricted source material under the original access conditions.
Deduplication and overlap
Deduplicate exact bytes first, then source identifiers, then economically equivalent events. Do not use a single name-and-amount key as the final rule. The same amount can recur in renewals or separate facilities, while currency conversion can make the same facility appear different. Retain separatedocument_count, source_row_count, registration_count, entity_count, facility_count, event_count and outcome_linked_facility_count. Record the number of uncertain matches and exclusions. A link that merges two facilities must preserve its evidence and be reversible.
For cross-source overlap, distinguish an exact duplicate, a confirming observation, an amendment and an unrelated event. Québec and federal corporate records can describe the same legal entity. EDC support can accompany a syndicated facility disclosed by an issuer. These records add corroboration, not necessarily another borrower or loan.