Triple
T32158408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand active fault database |
E821359
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geospatial database |
C60586
|
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 database Context triple: [New Zealand active fault database, instanceOf, geospatial database]
-
A.
spatial database extender
A spatial database extender is a software component that adds support for storing, querying, and analyzing spatial and geographic data within a traditional database system.
-
B.
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.
-
C.
geospatial company
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.
-
D.
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.
-
E.
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.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:32 a.m.