Triple
T36484878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MDA Space Missions |
E898909
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space technology company division |
C64051
|
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: space technology company division Context triple: [MDA Space Missions, instanceOf, space technology company division]
-
A.
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.
-
B.
space science division
The space science division is an organizational unit dedicated to researching, analyzing, and advancing knowledge about outer space, celestial bodies, and related physical phenomena.
-
C.
technology company division
chosen
A technology company division is an organizational unit within a tech firm that focuses on a specific product line, market segment, or functional area, managing its own strategy, development, and operations while aligning with the company’s overall goals.
-
D.
space services company
A space services company is an organization that provides commercial solutions related to space activities, such as launch services, satellite deployment and operations, in-orbit logistics, data services, and mission support for government, commercial, and research customers.
-
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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.