Triple
T18368801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aerospace Systems Division |
E440124
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace manufacturer 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 manufacturer division Context triple: [Aerospace Systems Division, instanceOf, aerospace manufacturer division]
-
A.
aerostructures manufacturer
An aerostructures manufacturer designs, engineers, and produces critical aircraft structural components—such as fuselages, wings, and empennages—for commercial, military, and aerospace applications.
-
B.
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.
-
C.
business aviation company division
A business aviation company division is an organizational unit within a larger aviation enterprise that focuses on providing private air travel services, fleet management, and related support specifically for corporate and high-net-worth clients.
-
D.
Collins Aerospace division
A Collins Aerospace division is an organizational unit within Collins Aerospace responsible for specific product lines, technologies, or market segments in the aerospace and defense industry.
-
E.
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.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:38 a.m.