Triple
T36487411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OCM |
E898969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite imaging sensor |
C28991
|
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: satellite imaging sensor Context triple: [OCM, instanceOf, satellite 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.
remote sensing satellite
chosen
A remote sensing satellite is an orbiting spacecraft equipped with sensors that collect data about the Earth's surface and atmosphere for applications such as mapping, environmental monitoring, and resource management.
-
C.
space surveillance sensor
A space surveillance sensor is a device or system that detects, tracks, and characterizes objects in space to support situational awareness, collision avoidance, and space traffic management.
-
D.
multispectral scanner
A multispectral scanner is a remote sensing device that captures image data across multiple specific wavelength bands of the electromagnetic spectrum to analyze and distinguish materials or features based on their spectral signatures.
-
E.
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.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.