Triple
T15830104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Station Explorer for X-ray Timing and Navigation Technology |
E383846
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technology demonstration mission |
C8801
|
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: technology demonstration mission Context triple: [Station Explorer for X-ray Timing and Navigation Technology, instanceOf, technology demonstration mission]
-
A.
space mission
chosen
A space mission is a planned and coordinated endeavor to send spacecraft, instruments, or humans beyond Earth's atmosphere to achieve specific scientific, exploratory, commercial, or technological objectives.
-
B.
space technology development program
A space technology development program is an organized initiative that researches, designs, tests, and matures advanced space-related technologies to enable or enhance future space missions and capabilities.
-
C.
space technology
Space technology encompasses the tools, systems, and methods used to explore, utilize, and operate in outer space, including spacecraft, satellites, launch vehicles, and supporting ground infrastructure.
-
D.
space technology
Space technology encompasses the tools, systems, and methods developed to explore, utilize, and operate in outer space, including spacecraft, satellites, launch vehicles, and supporting ground infrastructure.
-
E.
technology transfer mission
A technology transfer mission is a coordinated effort to share, adapt, and implement knowledge, tools, or innovations from one organization or context to another to enhance capabilities and outcomes.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:49 a.m.