Records and filters
Filter instruments, join positions and inspect event timestamps.
SQL referenceCapital markets · Research and record context
Connect instruments, issuers, events and research documents so analysts can inspect the records behind a question.
Start with an instrument's recorded issuer. Inspect the linked event, filing and research note without losing the document version each passage came from.
“Reporting period: Q1.”
“Reporting period: Q2.”
The application can show the cited version alongside the correction for review.
All identifiers and passages are illustrative. Source versions are records your ingestion pipeline maintains; they are not an automatic historical snapshot of every data model.
5 use cases / Capital markets
Start with the combination that fits your question. These are recommended starting points; the best fit depends on your data and query patterns.
| Use case | Recommended modalities | Why this combination fits |
|---|---|---|
| Order and trade analysis Inspect trading activity by instrument, account and period. | SQL filters and joins order and trade records, then aggregates the selected activity for analysis. | |
| Entity and ownership exploration Trace relationships between issuers, entities and instruments. | SQL supplies entity and instrument attributes. Graph traverses the ownership and issuance relationships in your data. | |
| Surveillance case evidence Explore related accounts and search the documents attached to a case. | SQL narrows recorded activity, Graph follows account and entity links, and FTS locates references in case evidence. | |
| Filings and research retrieval Find relevant passages across filings and research publications. | FTS matches names and phrases; Vector finds similar themes. SQL provides issuer, date and document-version context. | |
| Connected research workspace Expand a research result into its issuer network and supporting sources. | FTS and Vector retrieve source passages, Graph expands issuer relationships, and SQL supplies dated instrument and document records. |
Combine query results in your application using shared record IDs. Keep text indexes and embeddings updated as the source data changes.
A role for each model
Use source IDs to connect the results in your research application.
Filter instruments, join positions and inspect event timestamps.
SQL referenceTraverse declared instrument, issuer and related-entity references.
Graph schemaFind exact wording or rank matching passages in indexed source text.
Full-text referenceRetrieve research text using supplied embeddings, then inspect its source.
Vector schemaBegin with a sample issuer, its instruments and a document that has been revised.
Store publication time, ingestion time and source revision as explicit fields. The application chooses which version a query should use.
Schema referenceAttach document and revision IDs to text and embeddings. Write each index through its own endpoint and track source updates in ingestion.
Index document textCheck whether a result resolves to its original passage after a correction. Apply your application's data entitlements and retain the cited version.
Authentication referenceThe database supplies record context and retrieval. Market interpretation and any resulting action remain with your application and analysts.
Review your data flow