Triple
T33437143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoSPARQL |
E856262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geospatial query language |
C61224
|
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 query language Context triple: [GeoSPARQL, instanceOf, geospatial query language]
-
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.
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.
-
C.
PostGIS spatial function
A PostGIS spatial function is a database function that performs geometric or geographic operations—such as measuring distances, testing spatial relationships, or transforming coordinate systems—on spatial data stored in a PostgreSQL database.
-
D.
graph query language
A graph query language is a specialized language used to retrieve, manipulate, and analyze data stored as nodes and relationships in graph databases.
-
E.
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.
- F. None of above. chosen
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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.