Triple
T34674689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cuSpatial |
E890463
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geospatial data processing library |
C29100
|
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 data processing library Context triple: [cuSpatial, instanceOf, geospatial data processing library]
-
A.
geospatial database
A geospatial database is a specialized database system designed to store, query, and analyze spatial and geographic data such as coordinates, shapes, and locations.
-
B.
GIS software
chosen
GIS software is a type of computer application that captures, stores, analyzes, and visualizes geographic and spatial data to support mapping and spatial decision-making.
-
C.
geospatial data standard framework
A geospatial data standard framework is a structured set of guidelines, models, and protocols that ensure consistent representation, exchange, and interoperability of location-based data across systems and organizations.
-
D.
geospatial query language
A geospatial query language is a specialized language for expressing, filtering, and analyzing spatial data and relationships (such as distance, containment, and intersection) over geographic or geometric datasets.
-
E.
geospatial analytics initiative
A geospatial analytics initiative is a coordinated effort to collect, integrate, and analyze location-based data to generate spatial insights that inform strategic decision-making and operational improvements.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.