Triple
T16049760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIL-STD-1773 |
E389322
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | data bus 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: data bus standard Context triple: [MIL-STD-1773, instanceOf, data bus standard]
-
A.
serial bus interface standard
A serial bus interface standard defines the electrical, timing, and protocol rules that govern how devices communicate and exchange data over a serial communication bus.
-
B.
parallel computer bus
A parallel computer bus is a communication system that transfers multiple bits of data simultaneously across multiple wires or channels between components within a computer system.
-
C.
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.
-
D.
JEDEC standard
A JEDEC standard is a formal specification developed by the JEDEC Solid State Technology Association that defines common requirements and guidelines for the design, performance, testing, and interoperability of semiconductor and microelectronic components.
-
E.
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.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:56 a.m.