Triple
T29182909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARINC 653 |
E739790
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | avionics software standard |
C39921
|
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: avionics software standard Context triple: [ARINC 653, instanceOf, avionics software standard]
-
A.
ARINC specification
chosen
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.
avionics system
An avionics system is an integrated collection of electronic hardware and software on an aircraft that manages navigation, communication, monitoring, and control functions to ensure safe and efficient flight operations.
-
E.
avionics data bus
An avionics data bus is a communication system within an aircraft that transfers digital data between avionics components, such as sensors, flight computers, and control systems, to ensure coordinated and reliable operation.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 11:58 a.m.