Keep identities and dates explicit.
Model fund IDs, holdings, issuers, and source versions as rows. Query the fields your application uses to select an appropriate reporting period.
Define the schema All industries Connect the holding.
Mutual funds
Connect the holding.
Keep the source.
Bring fund records, issuer relationships, and searchable disclosures into your research and investor-service applications.
A path from position to publication
Know what connects—and which version you read.
Follow declared holding and issuer relationships, then retrieve the disclosure passages relevant to the analyst’s question.
Research question
Which source documents relate to this fund’s holdings?
- FundResearch fund
F-01has holding → - HoldingEquity position
H-21issued by → - IssuerNorthbridge Industries
I-07has disclosure → - DisclosureIssuer report
D-12Source ID retained
Document history
Same source. A new revision.
Your application decides which version is eligible for retrieval.
Version 2Archived
Preserved for earlier research records.
D-12:v2Version 3Selected for review
Passages linked to this document version.
D-12:v3Application assembles
- Holding and issuer records
- Matching disclosure passages
- Document ID, version, and location
Relationships provide context; they do not establish investment merit. The application combines separate queries, selects source versions, and leaves interpretation to the analyst.
Build source-linked retrieval5 use cases / Mutual funds
The right modalities for your workflow.
Start with the combination that fits your question. These are recommended starting points; the best fit depends on your data and query patterns.
- SQL Filter, join and aggregate records
- Graph Follow relationships between records
- FTS · Full-text search Find keywords, phrases and exact wording
- Vector Find similar items or meaning
| Use case | Recommended modalities | Why this combination fits |
|---|---|---|
| Fund operations reporting Inspect subscriptions, redemptions and imported valuation records. | SQL filters records by fund and date, aggregates flows and retrieves the underlying transactions. | |
| Holdings and issuer exposure Follow a fund's holdings to their issuers and related entities. | SQL selects dated position records. Graph connects funds, instruments and issuers through declared relationships. | |
| Scheme document search Find relevant terms in scheme documents and factsheets. | SQL identifies the scheme and publication version. FTS finds phrases and named terms in the indexed text. | |
| Distribution servicing context Connect an investor request to distributors, holdings and correspondence. | SQL supplies request and holding records, Graph follows distributor relationships, and FTS searches the related correspondence. | |
| Fund research retrieval Find research passages relevant to a fund or investment theme. | FTS matches names and terminology, Vector finds related themes, and SQL supplies fund attributes and publication dates. |
Combine query results in your application using shared record IDs. Keep text indexes and embeddings updated as the source data changes.
Define the data before the answer
Give each model a clear job.
Start with one fund, a reviewed set of holdings, and versioned source documents. Record both source dates and ingestion times; test missing and superseded material before expanding coverage.
Declare the paths you need.
Connect holding records to funds and issuers using schema relations. Traverse those paths to gather related records.
Create relationshipsIndex disclosure passages.
Generate embeddings in your pipeline. Keep vector IDs tied to passage rows, and evaluate results against questions your analysts have reviewed.
Set up semantic searchKeep words and sources together.
Index text separately for keyword retrieval. When a document changes, refresh its rows, embeddings, and text entries through their separate calls.
Add full-text searchStart with a source you can verify