Triple
T17541708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | landing of Space Shuttle Columbia STS-3 |
E427214
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Space Shuttle landing |
C39081
|
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 Shuttle landing Context triple: [landing of Space Shuttle Columbia STS-3, instanceOf, Space Shuttle landing]
-
A.
Space Shuttle mission
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 shuttle orbiter
A space shuttle orbiter is a reusable winged spacecraft designed to carry crew and cargo to and from low Earth orbit, operate as an orbital laboratory or platform, and then re-enter the atmosphere and land like an airplane.
-
C.
NASA spaceport
A NASA spaceport is a specialized aerospace facility where NASA prepares, launches, and sometimes recovers spacecraft and launch vehicles for missions into space.
-
D.
Space Shuttle Endeavour
Space Shuttle Endeavour is a retired NASA orbiter that served as a reusable spacecraft for transporting astronauts, satellites, and scientific payloads to and from low Earth orbit as part of the Space Shuttle program.
-
E.
lunar landing mission
A lunar landing mission is a coordinated spaceflight operation designed to transport a spacecraft from Earth to the Moon, achieve a controlled descent and landing on the lunar surface, conduct scientific or exploratory activities, and safely return data and/or crew.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:49 a.m.