Triple
T805525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merlin 1A |
E17423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | liquid-fueled rocket engine |
C6086
|
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: liquid-fueled rocket engine Context triple: [Merlin 1A, instanceOf, liquid-fueled rocket engine]
-
A.
liquid-fueled rocket
A liquid-fueled rocket is a propulsion system that burns liquid propellants—typically a fuel and an oxidizer stored in separate tanks—to produce high-velocity exhaust and generate thrust.
-
B.
liquid-cooled aircraft engine
A liquid-cooled aircraft engine is a piston or reciprocating powerplant that uses a circulating liquid coolant, typically water or glycol, to absorb and dissipate heat from the engine cylinders and heads, enabling efficient temperature control and reliable operation in flight.
-
C.
liquid-cooled aero engine
A liquid-cooled aero engine is an aircraft powerplant that uses a circulating liquid coolant, typically water or glycol, to absorb and dissipate heat from the engine, enabling higher performance and more consistent operating temperatures than air-cooled designs.
-
D.
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.
-
E.
expendable launch vehicle
An expendable launch vehicle is a rocket designed for a single use to deliver payloads such as satellites or spacecraft into space, after which its components are discarded rather than recovered or reused.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:38 p.m.