Triple
T19425531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AAR-02-01 |
E485970
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation accident report |
C41738
|
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 accident report Context triple: [AAR-02-01, instanceOf, aviation accident report]
-
A.
aviation accident
An aviation accident is an unplanned event associated with the operation of an aircraft that results in serious damage, injury, or loss of life.
-
B.
aviation accident or incident
An aviation accident or incident is an unplanned event associated with the operation of an aircraft that compromises or has the potential to compromise safety, resulting in damage, injury, or significant operational disruption.
-
C.
airline accident
An airline accident is an unplanned event involving an aircraft during operation that results in significant damage, serious injury, or loss of life.
-
D.
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.
-
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. chosen
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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:37 p.m.