Triple
T9179927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power and Controls |
E220295
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace systems division |
C5661
|
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 systems division Context triple: [Power and Controls, instanceOf, aerospace systems division]
-
A.
aerospace engineering subsystem
An aerospace engineering subsystem is a specialized, interrelated component or functional unit within an aerospace vehicle or system (such as propulsion, avionics, or thermal control) that performs a distinct set of engineering tasks to support overall mission objectives.
-
B.
aerospace corporation
An aerospace corporation is a large-scale enterprise that designs, manufactures, and services aircraft, spacecraft, and related systems and technologies for commercial, military, and space applications.
-
C.
aerospace organization
chosen
An aerospace organization is an entity that researches, designs, manufactures, operates, or supports aircraft, spacecraft, and related systems and technologies for commercial, governmental, or defense purposes.
-
D.
NASA division
A NASA division is an organizational unit within NASA responsible for managing specific programs, research areas, or operational functions to support the agency’s overall space and aeronautics mission.
-
E.
defense contractor division
A defense contractor division is an organizational unit within a defense company responsible for developing, producing, and supporting specific military or security-related products, services, or programs for government and allied clients.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:23 p.m.