Triple
T27356673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Development Flight Instrumentation |
E685703
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | flight test instrumentation 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: flight test instrumentation system Context triple: [Development Flight Instrumentation, instanceOf, flight test instrumentation system]
-
A.
flight test operations
Flight test operations encompass the planning, execution, monitoring, and analysis of test flights to evaluate and validate aircraft performance, safety, and regulatory compliance.
-
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.
flight test center
A flight test center is a specialized facility where aircraft, spacecraft, or related systems are systematically tested, evaluated, and validated under controlled conditions to ensure performance, safety, and regulatory compliance.
-
D.
flight test engineering course
A flight test engineering course teaches the principles, methods, and tools used to plan, conduct, analyze, and report aircraft and aerospace system flight tests.
-
E.
aviation training system
An aviation training system is an integrated platform that delivers theoretical instruction, practical simulation, performance assessment, and certification support to develop and maintain pilots’ and aviation personnel’s operational competencies and safety standards.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 11:51 a.m.