Triple
T10330074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WMS |
E242851
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Open Geospatial Consortium standard |
C27884
|
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: Open Geospatial Consortium standard Context triple: [WMS, instanceOf, Open Geospatial Consortium standard]
-
A.
open standard
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.
-
B.
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.
-
C.
ISO/IEC standard
An ISO/IEC standard is a formally agreed-upon specification developed jointly by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) that defines common requirements, guidelines, or characteristics for products, services, or systems to ensure quality, safety, interoperability, and consistency across international markets.
-
D.
geographic markup language
Geographic Markup Language is an XML-based standard for encoding, storing, and exchanging geographic information and spatial features on the web.
-
E.
W3C initiative
A W3C initiative is a coordinated effort or program led by the World Wide Web Consortium to develop, standardize, and promote open web technologies and best practices.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:52 a.m.