Triple
T32774865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ares IV mission (planned) |
E838168
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | crewed Mars mission in fiction |
C37760
|
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: crewed Mars mission in fiction Context triple: [Ares IV mission (planned), instanceOf, crewed Mars mission in fiction]
-
A.
Mars mission element
A Mars mission element is a distinct component, system, or phase of a Mars exploration mission (such as spacecraft, landers, habitats, or support infrastructure) that contributes specific functions toward achieving the mission’s overall objectives.
-
B.
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.
-
C.
crewed interstellar expedition
A crewed interstellar expedition is a long-duration space mission in which humans travel beyond their home star system to explore, study, or potentially settle distant stellar destinations.
-
D.
spaceship in fiction
A spaceship in fiction is a technologically advanced vehicle designed for travel through outer space, often serving as a setting, plot device, or symbol of exploration and conflict in speculative narratives.
-
E.
Mars system mission
chosen
A Mars system mission is a spaceflight endeavor designed to explore Mars and its surrounding environment, including its moons, atmosphere, surface, and potential for past or present life.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:13 a.m.