Triple
T16946712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 19111 |
E411085
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Geospatial standard |
C38290
|
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 standard Context triple: [ISO 19111, instanceOf, Geospatial standard]
-
A.
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.
-
B.
geodetic standard
A geodetic standard is an agreed-upon reference framework, model, or set of conventions used to define positions, shapes, and measurements on or near the Earth’s surface consistently and accurately.
-
C.
IHO standard
An IHO standard is an internationally agreed set of specifications and guidelines issued by the International Hydrographic Organization to ensure uniformity, reliability, and interoperability in hydrographic data, charts, and related maritime information.
-
D.
geospatial information unit
A geospatial information unit is a conceptual entity that encapsulates location-based data, attributes, and spatial relationships for a specific geographic feature or area.
-
E.
geographic markup language
Geographic Markup Language is an XML-based standard for encoding, storing, and exchanging geographic information and spatial features on the web.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.