Triple
T12032302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IATA Safety Audit for Ground Operations |
E286442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation safety standard |
C10446
|
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: aviation safety standard Context triple: [IATA Safety Audit for Ground Operations, instanceOf, aviation safety standard]
-
A.
aviation regulatory framework
The aviation regulatory framework is the structured set of laws, standards, and oversight mechanisms that govern the safe, efficient, and environmentally responsible operation of civil aviation activities.
-
B.
aviation safety audit program
chosen
An aviation safety audit program is a systematic, structured process for evaluating and verifying an aviation organization’s compliance with safety regulations, standards, and best practices to identify risks and drive continuous safety improvement.
-
C.
aviation safety plan
An aviation safety plan is a structured, organization-wide framework that identifies hazards, assesses and mitigates risks, and defines procedures and responsibilities to ensure the safe operation of aviation activities.
-
D.
aviation law
Aviation law is the body of rules, regulations, and international agreements that govern the operation, safety, security, and economic aspects of air travel and aircraft use.
-
E.
aviation safety notice
An aviation safety notice is an official communication that alerts aviation personnel to potential or known safety hazards, procedural changes, or risk mitigation measures to prevent accidents and incidents.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.