Triple
T19780752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ILS on runway 28 |
E475123
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | instrument landing system |
C41206
|
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: instrument landing system Context triple: [ILS on runway 28, instanceOf, instrument landing system]
-
A.
Instrument landing system
chosen
An instrument landing system is a ground-based radio navigation aid that provides precise lateral and vertical guidance to aircraft approaching and landing on a runway, especially in low-visibility conditions.
-
B.
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.
-
C.
integrated avionics suite
An integrated avionics suite is a cohesive collection of aircraft electronic systems—such as navigation, communication, flight control, and monitoring—designed to work together through shared hardware, software, and data networks to enhance safety, efficiency, and pilot situational awareness.
-
D.
rotorcraft lander
A rotorcraft lander is a vertical-takeoff-and-landing spacecraft or planetary probe that uses powered rotors instead of rockets or wings to descend, land, and maneuver near a surface.
-
E.
laser altimeter
A laser altimeter is a remote sensing instrument that measures the distance from the sensor to a surface by timing the round-trip travel of laser pulses, enabling precise elevation or topographic mapping.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:49 p.m.