Triple
T28716902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ares program |
E729984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional Mars exploration program |
C1591
|
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: fictional Mars exploration program Context triple: [Ares program, instanceOf, fictional Mars exploration program]
-
A.
fictional military program
A fictional military program is an imagined, often secretive initiative or project within an armed forces setting, designed to explore advanced technologies, strategies, or operations that drive the narrative in speculative or military-themed stories.
-
B.
fictional planet
A fictional planet is an imagined celestial world, often with its own unique geography, ecosystems, cultures, and physical laws, created to serve as the setting for stories or speculative scenarios.
-
C.
planetary exploration program
chosen
A planetary exploration program is an organized, long-term initiative that plans, funds, and conducts missions to study other planets and celestial bodies using robotic or crewed spacecraft.
-
D.
fictional space exploration organization
A fictional space exploration organization is an imagined institution—such as an agency, corporation, or coalition—dedicated to planning, funding, and conducting missions beyond Earth for purposes like discovery, colonization, defense, or scientific advancement.
-
E.
Mars system mission
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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:51 a.m.