Prediction Topics API
Keep subjects, horizons, and uncertainty in the record.
TOPIC GUIDE / 08
Financial documents mix subjects, organizations, instruments, and reporting periods. A careful topic model keeps those concepts distinct and preserves the source context needed to interpret each document.

Corporate reporting is a subject; a named issuer is an entity; a reported amount is a value with a unit and period. Each serves a different retrieval need. A document can mention several companies while being principally about one reporting issue.
Use separate fields for organizations, instruments, currencies, and topic concepts. Avoid guessing an identifier from an ambiguous name. If a symbol or abbreviation cannot be resolved from the source context, preserve the ambiguity for review.
A document’s publication date is not necessarily the period its figures describe. Retain both when they are available. A revised filing may refer to an earlier period, and a comparison may combine several periods within one document.
When extracting a statement, keep the relevant context with it. A number without its unit, period, and source can become misleading when displayed elsewhere. Topic classification should help retrieve the document without stripping away what the statement means.
Useful subjects might include financial reporting, corporate actions, market structure, or disclosure methods. Define each according to the content people need to find. Avoid designing a vocabulary solely from whatever words appear frequently in headlines.
Separate article type from subject. Commentary, an official filing, and a general explainer can all concern the same topic. Preserving that distinction helps readers understand the kind of evidence they are viewing before they interpret the details.
Review labels that could change how a sensitive statement is understood. A document may quote a forecast, discuss a risk factor, or describe a hypothetical scenario without asserting that the event occurred. Preserve attribution and conditional language.
The purpose of this guide is information architecture for financial content. Topic labels do not establish the accuracy of a financial statement or the suitability of an investment. Build a workflow that keeps the original source available and assigns an explicit review state when context is incomplete.
This example highlights fields worth discussing when you design your own contract. Define their meanings, allowed values, and review rules before an application relies on them.
| FIELD | PURPOSE |
|---|---|
document_type | Filing, commentary, or explainer |
entity_references | Organizations or instruments mentioned |
reporting_period | Period described by the content |
source_reference | Origin of the statement |
{
"document_type": "example-report",
"topic_ids": [
"finance.reporting"
],
"entity_references": [
"example-issuer"
],
"reporting_period": "example-period",
"source_reference": "example-document"
}Illustrative schema and example values; adapt them to your data and review process.
This guide covers the organization of financial content. Price feeds, financial statements, and other data sources have their own contracts and provenance requirements.
Do not assume that it can. Preserve the context needed to resolve an identifier and review ambiguous or incomplete references.
Only if the source supports that event classification under your policy. A hypothetical risk and a reported occurrence should remain distinguishable.
CONNECTED TOPICS
Keep subjects, horizons, and uncertainty in the record.
Connect stories to subjects without losing the event context.
Stable IDs, useful JSON, and a vocabulary built to evolve.