Triple
T36597800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloud Optimized GeoTIFF |
E902846
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | GeoTIFF profile |
C62321
|
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: GeoTIFF profile Context triple: [Cloud Optimized GeoTIFF, instanceOf, GeoTIFF profile]
-
A.
GIS data format
chosen
A GIS data format is a structured digital specification for storing, encoding, and exchanging geographic features and their associated spatial and attribute information.
-
B.
geographic information standard series
A geographic information standard series is a coordinated set of related standards that define consistent models, formats, and procedures for representing, exchanging, and managing geographic information.
-
C.
cartographic specification
A cartographic specification is a detailed set of rules and standards that defines how geographic data should be symbolized, generalized, and presented in a map to meet specific communication and design objectives.
-
D.
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.
-
E.
Open Geospatial Consortium standard
An Open Geospatial Consortium standard is a formally defined specification that ensures interoperability and consistent use, sharing, and processing of geospatial data and services across different systems and organizations.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.