Triple
T25012059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USHO |
E626016
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nautical charting agency |
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: nautical charting agency Context triple: [USHO, instanceOf, nautical charting agency]
-
A.
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.
-
B.
national mapping agency
A national mapping agency is a government organization responsible for producing, maintaining, and distributing authoritative geographic and cartographic information for an entire country.
-
C.
organ of the International Hydrographic Organization
An organ of the International Hydrographic Organization is a formal body or component within the IHO’s institutional structure that carries out specific functions such as governance, coordination, standard-setting, or advisory activities related to international hydrography and nautical charting.
-
D.
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.
-
E.
ship registry
A ship registry is an official record or database that documents and maintains detailed information about ships, including their ownership, identification, and legal status.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:05 a.m.