Triple
T28899847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DO-178B |
E732924
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation software standard |
C28398
|
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 software standard Context triple: [DO-178B, instanceOf, aviation software standard]
-
A.
ARINC specification
An ARINC specification is a standardized technical guideline developed by Aeronautical Radio, Inc. that defines interfaces, communication protocols, and equipment characteristics for avionics systems to ensure interoperability and reliability in aircraft.
-
B.
implementation mechanism for ICAO Standards and Recommended Practices
A structured set of legal, administrative, and technical processes through which States adopt, adapt, and apply ICAO Standards and Recommended Practices within their national civil aviation systems.
-
C.
ICAO standard
An ICAO standard is an internationally agreed set of rules, specifications, and recommended practices established by the International Civil Aviation Organization to ensure the safety, regularity, and efficiency of global civil aviation.
-
D.
aviation coding system
An aviation coding system is a structured set of standardized codes and rules used to represent, transmit, and interpret aviation-related information such as airports, routes, aircraft, and procedures in a consistent, machine-readable form.
-
E.
air transport industry standard
chosen
A formalized set of rules, guidelines, and technical specifications that ensure safety, interoperability, efficiency, and regulatory compliance across the global air transport industry.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 8:01 a.m.