Triple
T18274109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Rocket Module URM-1 |
E437689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | launch vehicle module |
C37295
|
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: launch vehicle module Context triple: [Universal Rocket Module URM-1, instanceOf, launch vehicle module]
-
A.
rocket launcher module
A rocket launcher module is a detachable system that stores, aims, and fires rockets, integrating guidance, power, and safety mechanisms for use on a vehicle, platform, or structure.
-
B.
space launch vehicle component
chosen
A space launch vehicle component is a physical subsystem or part—such as engines, tanks, avionics, or structural elements—that contributes to the propulsion, guidance, structural integrity, or support functions required to deliver payloads from Earth to space.
-
C.
orbital launch vehicle
An orbital launch vehicle is a rocket-powered system designed to transport payloads from Earth's surface into orbit by achieving sufficient velocity and altitude to remain in continuous free-fall around the planet.
-
D.
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.
-
E.
launch vehicle payload
A launch vehicle payload is the cargo—such as satellites, scientific instruments, or crewed spacecraft—that a rocket is designed to transport from Earth to a specified orbit or trajectory 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:34 a.m.