Triple
T21480012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network & Space Systems |
E529962
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Boeing division |
C44838
|
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: Boeing division Context triple: [Network & Space Systems, instanceOf, Boeing division]
-
A.
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.
-
B.
McDonnell Douglas aircraft
McDonnell Douglas aircraft are a family of commercial and military airplanes known for their distinctive designs, such as the DC-9/MD-80 series and F-15 fighter, produced by the former American aerospace manufacturer McDonnell Douglas before its merger with Boeing.
-
C.
Douglas aircraft
Douglas aircraft are a series of commercial and military airplanes designed and manufactured by the Douglas Aircraft Company, known for their significant impact on aviation history through models like the DC airliners and C-series transports.
-
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.
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.
- F. None of above. chosen
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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:20 p.m.