Triple
T15200964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freycinet gauge |
E363265
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | waterway standard |
C15334
|
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: waterway standard Context triple: [Freycinet gauge, instanceOf, waterway standard]
-
A.
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.
-
B.
navigable waterway
A navigable waterway is a natural or artificial body of water, such as a river, canal, or channel, that is deep and wide enough for vessels to travel safely for transportation or commerce.
-
C.
hydrography standard
chosen
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.
-
D.
water quality standard
A water quality standard is a regulatory benchmark that defines acceptable concentrations of pollutants and conditions in water bodies to protect human health, aquatic life, and environmental integrity.
-
E.
waterway network
A waterway network is an interconnected system of natural and artificial water channels (such as rivers, canals, and streams) designed or utilized for the movement, distribution, and management of water and waterborne transport.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:10 a.m.