Triple
T18599928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FASB Statements of Financial Accounting Concepts |
E454592
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | accounting standard-setting document |
C2034
|
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-setting document Context triple: [FASB Statements of Financial Accounting Concepts, instanceOf, accounting standard-setting document]
-
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.
standards-related document
chosen
A standards-related document is an authoritative publication that defines, explains, or supports the development, implementation, or interpretation of technical or organizational standards.
-
C.
standards-setting organization
A standards-setting organization is an entity that develops, maintains, and promotes agreed-upon technical, professional, or procedural norms to ensure compatibility, quality, and interoperability across industries or sectors.
-
D.
standardized legal document
A standardized legal document is a pre-formatted, legally binding template with uniform structure and language designed for repeated use in similar transactions or situations.
-
E.
regulatory document
A regulatory document is an official written instrument issued by an authority that defines, interprets, or enforces rules, standards, or requirements governing specific activities, entities, or domains.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.