Market-data lake

lake.institutional_filings dataset schema

Column types and research semantics for NexusTrade’s lake.institutional_filings dataset. Read the supported schema before submitting a bounded SQL query.

Query name
lake.institutional_filings
Grain
year
Columns
15

Columns and types

These columns come from the same versioned logical catalog used by the query validator and engine. They describe the fields you can query. Some historical rows have missing values; fields absent from older shards can return typed NULL.

accessionVARCHAR
filingDateDATE
availableAtTIMESTAMP
availabilitySourceVARCHAR
submissionTypeVARCHAR
cikVARCHAR
managerNameVARCHAR
periodOfReportDATE
reportCalendarOrQuarterVARCHAR
isAmendmentBOOLEAN
amendmentNoVARCHAR
amendmentTypeVARCHAR
dateReportedDATE
rawArchiveKeyVARCHAR
sourceUrlVARCHAR

Current logical schema for lake.institutional_filings

Coverage and timing

The logical view is backed by canonical manifest-resolved data. Query this name rather than guessing a physical database collection or object-storage path.

`availableAt` is the point-in-time column: a row may inform a decision only when `availableAt <= as_of`. It is the end of the SEC filing date in America/New_York. Never use `periodOfReport` as availability — originals file at p50 42 days after period-end (the 45-day rule, measured). One row per 13F submission: `submissionType` is 13F-HR, 13F-HR/A (amendment), 13F-NT (notice, no holdings) or 13F-NT/A. Amendments are versioned rows with their own `availableAt`; originals are never overwritten. `isAmendment`, `amendmentNo`, `amendmentType` carry the chain. `cik` is the filing manager's CIK and `managerName` their name as filed. `periodOfReport` is the holdings snapshot date — what the manager held then, not when anyone could know. `sourceUrl` is the filing's SEC EDGAR index page keyed by manager `cik` (not an issuer): https://www.sec.gov/Archives/edgar/data/{cik without leading zeros}/{accession without dashes}/{accession}-index.htm.

Run a limited query

Use a registered API key with lake scope. Select needed columns, bind user-supplied values and restrict dates when the table has a time dimension. Query results are durable parts with a schema and manifest rather than an unbounded in-memory array.

This reference documents the schema and its meaning. Run queries in your signed-in workspace; this page does not execute SQL or show private results and datasets.

sql
SELECT "accession", "filingDate", "availableAt"
FROM lake.institutional_filings
LIMIT 20;