Triple
T19469050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government Auditing Standards |
E487075
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | audit standard |
C2899
|
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: audit standard Context triple: [Government Auditing Standards, instanceOf, audit standard]
-
A.
internal auditing standard
An internal auditing standard is a formalized set of principles, guidelines, and procedures that govern how internal audits are planned, executed, documented, and reported to ensure consistency, reliability, and compliance with organizational and regulatory expectations.
-
B.
audit law
Audit law is the body of legal rules and regulations that governs how financial audits are planned, conducted, reported, and overseen to ensure transparency, accuracy, and accountability in financial reporting.
-
C.
audit function
An audit function is a systematic process or mechanism used to independently examine, verify, and evaluate records, operations, or controls to ensure accuracy, compliance, and effectiveness.
-
D.
software review and audit standard
chosen
A software review and audit standard is a formalized set of criteria, processes, and guidelines used to systematically evaluate software products and development practices for quality, compliance, security, and reliability.
-
E.
audit division
The audit division is an organizational unit responsible for independently examining and evaluating financial records, operations, and internal controls to ensure accuracy, compliance, and effective risk management.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:39 p.m.