Triple
T11000862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cascade, Smallsat and Ionospheric Polar Explorer |
E259999
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian space mission |
C11470
|
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: Canadian space mission Context triple: [Cascade, Smallsat and Ionospheric Polar Explorer, instanceOf, Canadian space mission]
-
A.
Canadian satellite
chosen
A Canadian satellite is a spaceborne device designed, built, or operated by Canada for purposes such as communications, Earth observation, scientific research, or navigation.
-
B.
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.
-
C.
International Space Station expedition
An International Space Station expedition is a long-duration mission during which a designated crew lives and works aboard the ISS to conduct scientific research, perform maintenance, and support ongoing space operations.
-
D.
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.
-
E.
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.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:25 p.m.