Triple
T18230098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARINC 664 |
E436522
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation Ethernet standard |
C14212
|
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 Ethernet standard Context triple: [ARINC 664, instanceOf, aviation Ethernet standard]
-
A.
Ethernet fronthaul standard
An Ethernet fronthaul standard defines the protocols, interfaces, and performance requirements for transporting radio access network (RAN) traffic between distributed radio units and centralized baseband units over Ethernet-based networks.
-
B.
avionics data bus
chosen
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.
-
C.
G.hn standard
The G.hn standard is a unified home networking specification that enables high-speed data transmission over existing wiring infrastructures such as power lines, phone lines, and coaxial cables within a building.
-
D.
Ethernet OAM standard
The Ethernet OAM standard defines protocols and mechanisms for monitoring, fault management, and performance management in Ethernet networks to ensure reliable and maintainable service operation.
-
E.
IEEE standard
An IEEE standard is a formally documented set of technical specifications and guidelines developed and maintained by the Institute of Electrical and Electronics Engineers to ensure interoperability, safety, and quality across electrical, electronic, and computing technologies.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:33 a.m.