Triple
T35140439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IOM Financial Report and Audited Financial Statements |
E1014689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial report |
C7066
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: financial report Context triple: [IOM Financial Report and Audited Financial Statements, instanceOf, financial report]
-
A.
financial reporting issue
A financial reporting issue is any error, inconsistency, omission, or ambiguity in an organization’s financial statements or disclosures that may misrepresent its financial position, performance, or compliance with accounting standards.
-
B.
financial reporting framework
A financial reporting framework is a structured set of principles, standards, and rules that guide how an entity measures, recognizes, presents, and discloses financial information in its financial statements.
-
C.
financial domain
The financial domain encompasses all activities, institutions, markets, and instruments involved in managing, investing, and transferring money and other financial assets.
-
D.
economic report
An economic report is a structured document that analyzes and presents data, trends, and forecasts about economic conditions to inform decision-making by policymakers, businesses, and investors.
-
E.
annual financial statement
chosen
An annual financial statement is a comprehensive report summarizing an organization’s financial performance and position over a fiscal year, typically including the income statement, balance sheet, cash flow statement, and accompanying notes.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.