Triple
T11001957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Space Telescope servicing mission 1 |
E260023
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space telescope servicing mission |
C5891
|
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 telescope servicing mission Context triple: [Hubble Space Telescope servicing mission 1, instanceOf, space telescope servicing mission]
-
A.
Space Shuttle mission
chosen
A Space Shuttle mission is a coordinated spaceflight operation using the Space Shuttle orbiter to transport crew, cargo, and conduct scientific or technical objectives in Earth orbit and beyond.
-
B.
space telescope hardware
Space telescope hardware comprises the physical components—such as mirrors, detectors, support structures, and control systems—designed to operate in space to collect and transmit astronomical data beyond Earth’s atmosphere.
-
C.
space mission
A space mission is a planned and coordinated endeavor to send spacecraft, instruments, or humans beyond Earth's atmosphere to achieve specific scientific, exploratory, commercial, or technological objectives.
-
D.
International Space Station expedition
An International Space Station expedition is a long-duration mission during which a designated crew lives and works aboard the ISS to conduct scientific research, perform maintenance, and support ongoing space operations.
-
E.
spacecraft
A spacecraft is a vehicle or device designed to travel beyond Earth's atmosphere for purposes such as exploration, communication, research, or transportation.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:25 p.m.