Triple
T11693074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITS (Interplanetary Transport System) |
E277917
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conceptual space transportation architecture |
C1126
|
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: conceptual space transportation architecture Context triple: [ITS (Interplanetary Transport System), instanceOf, conceptual space transportation architecture]
-
A.
space transportation system
chosen
A space transportation system is an integrated set of vehicles, infrastructure, and operations designed to move payloads and passengers between Earth and space or between locations in space.
-
B.
spacecraft propulsion concept
A spacecraft propulsion concept is a theoretical or practical method for generating thrust to maneuver a spacecraft in space, encompassing the underlying physics, required systems, and performance characteristics.
-
C.
interstellar spacecraft design study
A conceptual analysis and planning effort that explores, evaluates, and defines the technologies, configurations, and mission architectures required for a feasible interstellar spacecraft.
-
D.
reusable spaceplane
A reusable spaceplane is a winged spacecraft designed to take off, operate, and land multiple times like an aircraft while transporting payloads or crew between Earth and space.
-
E.
uncrewed spaceflight
Uncrewed spaceflight is the operation of spacecraft without human passengers onboard, using automated systems and remote control to conduct missions such as exploration, observation, and technology testing in space.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:40 p.m.