Triple
T5355232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOXIE |
E102673
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | in-situ resource utilization technology demonstrator |
C18000
|
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: in-situ resource utilization technology demonstrator Context triple: [MOXIE, instanceOf, in-situ resource utilization technology demonstrator]
-
A.
Mars rover instrument
A Mars rover instrument is a specialized scientific device mounted on a Mars rover that measures, analyzes, or images the Martian environment and geology to support planetary research and exploration objectives.
-
B.
orbital test vehicle
An orbital test vehicle is a reusable or expendable spacecraft designed to conduct experimental missions in Earth orbit to validate technologies, systems, or operational concepts for future spaceflight applications.
-
C.
Mars mission engineering activity
Mars mission engineering activity encompasses the planning, design, testing, and integration of systems and technologies required to safely transport, land, and support missions on the Martian surface and in its orbit.
-
D.
ablative thermal protection system
An ablative thermal protection system is a heat shield that protects a spacecraft by sacrificially charring, melting, and eroding material to absorb and carry away extreme reentry heat.
-
E.
space station resupply vehicle
A space station resupply vehicle is a spacecraft designed to transport cargo, equipment, and sometimes crew to and from an orbiting space station, supporting its ongoing operations and maintenance.
- 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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 2:01 p.m.