Triple
T4078344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydrographic Services and Standards Committee |
E87418
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IHO body |
C4267
|
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: IHO body Context triple: [Hydrographic Services and Standards Committee, instanceOf, IHO body]
-
A.
oceanographic organization
An oceanographic organization is an entity dedicated to studying, monitoring, and managing the oceans and marine environments through scientific research, data collection, and related educational or policy activities.
-
B.
maritime navigation authority
chosen
A maritime navigation authority is an organization responsible for regulating, managing, and ensuring the safety and efficiency of vessel movements and navigational systems within designated waters.
-
C.
law of the sea institution
A law of the sea institution is an organization or body responsible for developing, interpreting, implementing, or enforcing legal rules and frameworks governing the use, management, and protection of the world’s oceans and marine resources.
-
D.
naval administrative office
A naval administrative office is an organizational unit responsible for managing the paperwork, personnel records, logistics, and regulatory compliance that support the operations of a navy or naval installation.
-
E.
meteorological organization
A meteorological organization is an entity responsible for observing, analyzing, and forecasting atmospheric conditions to support weather prediction, climate monitoring, and related public and scientific services.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:39 p.m.