Triple
T16966219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-124 Navigational Warnings product specification |
E411544
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime data standard |
C15332
|
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: maritime data standard Context triple: [S-124 Navigational Warnings product specification, instanceOf, maritime data standard]
-
A.
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.
-
B.
IHO standard
chosen
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.
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.
-
D.
standardized maritime form
A standardized maritime form is a pre-approved, uniform document used in shipping and marine operations to record, communicate, and legally formalize recurring transactions and procedures across the maritime industry.
-
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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.