Triple
T11078819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Space Telescope solar arrays |
E261934
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spacecraft solar array |
C15075
|
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 solar array Context triple: [Hubble Space Telescope solar arrays, instanceOf, spacecraft solar array]
-
A.
spacecraft power system
chosen
A spacecraft power system is the integrated set of components and subsystems that generate, store, condition, and distribute electrical energy to support all spacecraft functions throughout its mission.
-
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.
Mars rover instrument
A Mars rover instrument is a specialized scientific device mounted on a Mars rover that measures, analyzes, or images the Martian environment and geology to support planetary research and exploration objectives.
-
D.
spacecraft camera system
A spacecraft camera system is an integrated assembly of optical, sensor, processing, and control components designed to capture, process, and transmit images or video of space, celestial bodies, or spacecraft surroundings under the extreme conditions of spaceflight.
-
E.
heliophysics mission fleet
A heliophysics mission fleet is a coordinated collection of spacecraft and instruments designed to observe the Sun and its interactions with the solar system from multiple vantage points to better understand solar activity and space weather.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.