Triple
T6172758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeroscreen cockpit protection |
E137742
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cockpit protection system |
C14046
|
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: cockpit protection system Context triple: [Aeroscreen cockpit protection, instanceOf, cockpit protection system]
-
A.
defensive avionics system
A defensive avionics system is an integrated suite of onboard sensors, processors, and countermeasure devices designed to detect, identify, and protect an aircraft from hostile threats such as radar, missiles, and electronic attacks.
-
B.
avionics system
chosen
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.
ablative thermal protection system
An ablative thermal protection system is a heat shield that protects a spacecraft by sacrificially charring, melting, and eroding material to absorb and carry away extreme reentry heat.
-
D.
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.
-
E.
active head restraint system
An active head restraint system is a safety feature in vehicle seats that automatically moves the headrest forward and/or upward during a rear-end collision to reduce the risk of whiplash injuries.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:18 p.m.