Triple
T18566126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFRS 15 Revenue from Contracts with Customers |
E453764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Revenue recognition 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: Revenue recognition standard Context triple: [IFRS 15 Revenue from Contracts with Customers, instanceOf, Revenue recognition 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.
revenue service
A revenue service is a governmental or organizational entity responsible for assessing, collecting, and enforcing taxes or other forms of income to fund public operations and services.
-
C.
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.
-
D.
production accounting system
A production accounting system is a software solution that tracks, measures, and reconciles production volumes, inventories, and related financial values across the entire production lifecycle to ensure accurate reporting and cost control.
-
E.
publishing standard
A publishing standard is an agreed-upon set of rules and guidelines that define how content is formatted, structured, and shared across publishing systems to ensure consistency, interoperability, and quality.
- 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.