Triple
T2660462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IATA Operational Safety Audit |
E54713
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | operational safety audit |
C4530
|
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: operational safety audit Context triple: [IATA Operational Safety Audit, instanceOf, operational safety audit]
-
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.
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.
-
C.
occupational safety and health code of practice
chosen
An occupational safety and health code of practice is a structured set of guidelines and minimum standards that organizations must follow to systematically identify, control, and manage workplace hazards to protect workers’ health, safety, and welfare.
-
D.
operational concept
An operational concept is a high-level description of how a system, organization, or capability is intended to function in practice to achieve its objectives within a specific context.
-
E.
operational unit
An operational unit is an organized group, department, or component within a larger system that performs specific tasks or functions to achieve defined operational objectives.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:53 p.m.