Triple
T27356674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Development Flight Instrumentation |
E685703
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace test equipment |
C26742
|
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: aerospace test equipment Context triple: [Development Flight Instrumentation, instanceOf, aerospace test equipment]
-
A.
aerospace testing activity
An aerospace testing activity is a structured process of evaluating aerospace systems, components, or operations under controlled conditions to verify performance, safety, reliability, and compliance with specified requirements.
-
B.
electronic test equipment
chosen
Electronic test equipment comprises instruments and devices used to create, measure, and analyze electrical signals and parameters to verify the performance, functionality, and safety of electronic systems and components.
-
C.
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.
-
D.
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.
-
E.
NASA ground support equipment
NASA ground support equipment comprises the specialized tools, structures, and systems used on the ground to assemble, test, transport, service, and launch spacecraft and launch vehicles safely and reliably.
- 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.