Triple
T32256892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPOT Image |
E824049
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geospatial imagery provider |
C33874
|
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: geospatial imagery provider Context triple: [SPOT Image, instanceOf, geospatial imagery provider]
-
A.
geospatial web service
A geospatial web service is an online system that provides access to, processing of, and interaction with geographic data and spatial analyses over the web using standardized protocols.
-
B.
web mapping API
A web mapping API is a set of programmable interfaces that allow developers to embed, customize, and interact with digital maps and geospatial data within web applications.
-
C.
satellite-based Earth observation service
A satellite-based Earth observation service collects, processes, and delivers remotely sensed data about the Earth's surface and atmosphere to support applications such as environmental monitoring, resource management, and disaster response.
-
D.
geospatial company
chosen
A geospatial company is an organization that collects, analyzes, and applies location-based data and mapping technologies to provide insights, products, and services related to the Earth's surface and spatial relationships.
-
E.
remote sensing satellite
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.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:41 a.m.