Triple
T11064593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SARPs |
E261592
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Aviation regulatory instrument |
C4625
|
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 regulatory instrument Context triple: [SARPs, instanceOf, Aviation regulatory instrument]
-
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 discipline
Aviation discipline is the systematic body of knowledge, practices, and standards that govern the safe, efficient, and regulated operation, management, and study of aircraft and air transportation.
-
C.
aviation law
chosen
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.
-
D.
European Union aviation safety document
A European Union aviation safety document is an official regulatory or guidance text issued by EU institutions or agencies that sets standards, procedures, and requirements to ensure the safety of civil aviation operations within EU airspace and by EU operators.
-
E.
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.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:26 p.m.