Triple
T18566125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFRS 15 Revenue from Contracts with Customers |
E453764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Accounting standard |
C5322
|
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: Accounting standard Context triple: [IFRS 15 Revenue from Contracts with Customers, instanceOf, Accounting standard]
-
A.
accounting standard framework
An accounting standard framework is a structured set of principles, rules, and guidelines that govern how financial transactions are recorded, measured, presented, and disclosed in financial statements to ensure consistency, transparency, and comparability.
-
B.
financial reporting framework
chosen
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.
accounting department
The accounting department is the organizational unit responsible for recording, analyzing, and reporting a company’s financial transactions to ensure accuracy, compliance, and informed decision-making.
-
D.
accountant
An accountant is a professional who records, analyzes, and reports financial information to help individuals or organizations manage their finances and comply with regulations.
-
E.
corporate governance standard
A corporate governance standard is a formalized set of principles, rules, and best practices that guide how a corporation is directed, controlled, and held accountable to its stakeholders.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.