Triple
T25160042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shipping Board Bureau of the Department of Commerce |
E626410
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime regulatory body |
C18354
|
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 regulatory body Context triple: [Shipping Board Bureau of the Department of Commerce, instanceOf, maritime regulatory body]
-
A.
maritime navigation authority
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.
maritime jurisdictional office
chosen
A maritime jurisdictional office is a governmental or regulatory entity responsible for overseeing, enforcing, and administering laws, regulations, and policies within a defined maritime area or coastal zone.
-
C.
maritime safety regulation
Maritime safety regulation is the body of laws, standards, and procedures designed to prevent accidents, protect life, property, and the marine environment, and ensure safe operations in maritime activities.
-
D.
marine accident investigation body
A marine accident investigation body is an independent authority responsible for examining maritime incidents to determine causes, identify safety issues, and recommend measures to prevent future occurrences.
-
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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:31 a.m.