Triple
T3717170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Typhoon FGR4 mission systems |
E81558
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | integrated avionics suite |
C14169
|
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: integrated avionics suite Context triple: [Typhoon FGR4 mission systems, instanceOf, integrated avionics suite]
-
A.
integrated air defence system
An integrated air defence system is a coordinated network of sensors, command and control elements, and weapon systems designed to detect, track, and engage aerial threats to protect designated airspace and assets.
-
B.
attitude control computer
An attitude control computer is an onboard system that calculates and commands the necessary control actions to orient and stabilize a vehicle, such as a spacecraft or aircraft, in three-dimensional space.
-
C.
air and missile defense interceptor
An air and missile defense interceptor is a guided weapon system designed to detect, track, and destroy incoming aircraft, cruise missiles, or ballistic missiles before they reach their targets.
-
D.
flight simulation facility
A flight simulation facility is a specialized environment equipped with advanced simulators and support systems that replicate real-world aircraft operations for pilot training, research, and systems testing.
-
E.
spacecraft onboard computer
A spacecraft onboard computer is a specialized, radiation-hardened computing system that autonomously manages spacecraft functions, navigation, communication, and data handling in the harsh environment of space.
- F. None of above. chosen
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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:33 p.m.