Triple
T28708880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcanic Ash Advisories |
E729771
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation safety bulletin |
C22400
|
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 bulletin Context triple: [Volcanic Ash Advisories, instanceOf, aviation safety bulletin]
-
A.
aviation safety notice
chosen
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.
-
B.
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.
-
C.
aviation safety audit program
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.
-
D.
aviation accident report
An aviation accident report is a formal, structured document that records the circumstances, causes, findings, and safety recommendations related to an aircraft incident or accident.
-
E.
aviation safety collaboration
Aviation safety collaboration is the coordinated effort among regulators, airlines, manufacturers, airports, and other stakeholders to share data, align standards, and jointly implement practices that prevent accidents and enhance the safety of air travel.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:46 a.m.