Triple
T17790758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IHO S-130 |
E444153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hydrographic data standard family |
C15333
|
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: hydrographic data standard family Context triple: [IHO S-130, instanceOf, hydrographic data standard family]
-
A.
hydrographic data standard
chosen
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.
-
B.
hydrographic data model
A hydrographic data model is a structured representation of water-related geographic features, measurements, and relationships used to store, analyze, and manage hydrographic information such as rivers, lakes, coastlines, and bathymetry.
-
C.
hydrographic metadata framework
A hydrographic metadata framework is a structured system for defining, organizing, and managing standardized information about the collection, quality, and characteristics of hydrographic data such as bathymetry, currents, and tides.
-
D.
hydrographic standard
A hydrographic standard is an agreed-upon specification or set of rules that defines how water-related geographic data (such as depths, coastlines, and navigational features) are measured, recorded, formatted, and shared to ensure consistency and interoperability.
-
E.
hydrography standard
A hydrography standard is a formalized set of rules and specifications that define how water-related geographic features (such as rivers, lakes, and coastlines) are represented, measured, and exchanged in mapping and geospatial data systems.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:13 a.m.