Triple
T16921262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martian Moons eXploration mission |
E410448
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | JAXA mission |
C37759
|
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: JAXA mission Context triple: [Martian Moons eXploration mission, instanceOf, JAXA mission]
-
A.
NASA space mission
A NASA space mission is a coordinated, goal-driven endeavor planned and executed by NASA to explore, observe, or utilize space using specialized spacecraft, instruments, and supporting ground operations.
-
B.
NASA mission component
A NASA mission component is a distinct hardware, software, or operational element designed to perform a specific function that contributes to the overall objectives and success of a NASA space mission.
-
C.
Indian Space Research Organisation mission
An Indian Space Research Organisation mission is a coordinated spaceflight project planned, developed, and executed by ISRO to achieve specific scientific, technological, or strategic objectives in space exploration and utilization.
-
D.
Indian Space Research Organisation mission
An Indian Space Research Organisation mission is a coordinated spaceflight project planned, developed, and executed by ISRO to achieve specific scientific, technological, or operational objectives in space.
-
E.
Italian Space Agency mission
An Italian Space Agency mission is a coordinated space exploration or satellite project planned, funded, and managed by the Italian Space Agency (ASI) to achieve specific scientific, technological, or operational objectives in space.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:30 a.m.