Triple
T9857731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EASy flight deck |
E239629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | integrated flight deck |
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 flight deck Context triple: [EASy flight deck, instanceOf, integrated flight deck]
-
A.
integrated avionics suite
chosen
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.
-
B.
double-deck aircraft
A double-deck aircraft is a large passenger airplane featuring two full-length passenger decks stacked vertically within the fuselage to increase seating capacity and optimize space.
-
C.
observation deck
An observation deck is an elevated platform, often atop a tall building or structure, designed to provide visitors with expansive views of the surrounding area.
-
D.
deployable air command and control centre
A deployable air command and control centre is a mobile, rapidly configurable facility that provides the infrastructure, systems, and personnel needed to plan, direct, and coordinate air operations in a given theater.
-
E.
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.
- 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_69ca84e6493081909cf58c8d42ea856b |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:35 p.m.