Triple
T1701925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMO Member State Audit Scheme |
E36785
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | audit scheme |
C5267
|
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 scheme Context triple: [IMO Member State Audit Scheme, instanceOf, audit scheme]
-
A.
auditing system
An auditing system is a software component that systematically collects, records, and analyzes events or transactions within a system to ensure accountability, traceability, and compliance with policies or regulations.
-
B.
auditing institution
An auditing institution is an independent organization responsible for systematically examining and evaluating financial records, operations, and controls to ensure accuracy, compliance, and accountability.
-
C.
software review and audit standard
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.
-
D.
encryption scheme
An encryption scheme is a systematic method that transforms readable data into an unreadable form using algorithms and keys to ensure confidentiality, integrity, and secure communication.
-
E.
administrative oversight regime
chosen
An administrative oversight regime is a structured system of rules, procedures, and institutions designed to monitor, review, and correct the actions and decisions of administrative bodies to ensure legality, accountability, and fairness.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.