Triple
T10329928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geography Markup Language |
E242848
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | OGC standard |
C2624
|
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: OGC standard Context triple: [Geography Markup Language, instanceOf, OGC standard]
-
A.
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.
-
B.
open standard
chosen
An open standard is a publicly available specification, developed and maintained through a transparent, collaborative process, that can be implemented and used by anyone without restrictive licensing.
-
C.
geographic markup language
Geographic Markup Language is an XML-based standard for encoding, storing, and exchanging geographic information and spatial features on the web.
-
D.
hydrographic data standard
A hydrographic data standard is a formal specification that defines consistent formats, structures, and protocols for collecting, storing, exchanging, and interpreting water-related geographic and oceanographic information.
-
E.
official standard
An official standard is an authoritative, formally approved specification or guideline established by a recognized body to ensure consistency, compatibility, and quality across products, services, or processes.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:52 a.m.