Triple
T12175309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JWST Integrated Science Instrument Module |
E290072
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spacecraft structural element |
C11771
|
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: spacecraft structural element Context triple: [JWST Integrated Science Instrument Module, instanceOf, spacecraft structural element]
-
A.
launch vehicle upper structure
The launch vehicle upper structure is the integrated assembly above the core propulsion stages that houses the payload, guidance systems, and associated support hardware, ensuring structural integrity, environmental protection, and proper deployment during ascent and orbital insertion.
-
B.
spacecraft
A spacecraft is a vehicle or device designed to travel beyond Earth's atmosphere for purposes such as exploration, communication, research, or transportation.
-
C.
spacecraft payload adapter
A spacecraft payload adapter is a structural interface that securely connects a satellite or payload to the launch vehicle, ensuring proper alignment, load transfer, and separation during ascent and deployment.
-
D.
space component
chosen
A space component is a discrete, reusable element or module designed to perform a specific function within a larger space system or environment.
-
E.
Spacelab subsystem
A Spacelab subsystem is a distinct functional component of the Spacelab space laboratory that performs specialized tasks—such as power, life support, data handling, or experiment support—to enable and sustain scientific operations in orbit.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:50 p.m.