Triple
T16336458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRISM |
E396690
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | panchromatic imaging sensor |
C10675
|
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: panchromatic imaging sensor Context triple: [PRISM, instanceOf, panchromatic imaging sensor]
-
A.
spaceborne imaging spectrometer
A spaceborne imaging spectrometer is an instrument mounted on a satellite that captures images across many narrow, contiguous spectral bands to measure and analyze the spectral properties of Earth's surface and atmosphere.
-
B.
imager
chosen
An imager is a component or system that captures, generates, or processes visual representations of data, scenes, or objects into image form.
-
C.
speckle imaging camera
A speckle imaging camera is a specialized high-speed imaging device that captures many short-exposure frames to reconstruct high-resolution images by analyzing and processing speckle patterns caused by atmospheric or medium-induced distortions.
-
D.
spacecraft camera system
A spacecraft camera system is an integrated assembly of optical, sensor, processing, and control components designed to capture, process, and transmit images or video of space, celestial bodies, or spacecraft surroundings under the extreme conditions of spaceflight.
-
E.
multispectral targeting system
A multispectral targeting system is an integrated sensor and processing suite that detects, tracks, and designates targets across multiple parts of the electromagnetic spectrum (e.g., visible, infrared, and radar) to enhance accuracy and situational awareness.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.