Triple
T12876999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Board of Pilot Commissioners for the Bays of San Francisco, San Pablo and Suisun |
E307994
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime pilotage authority |
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: maritime pilotage authority Context triple: [Board of Pilot Commissioners for the Bays of San Francisco, San Pablo and Suisun, instanceOf, maritime pilotage authority]
-
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.
maritime jurisdictional office
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.
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.
-
D.
maritime designation
A maritime designation is a formal label or classification assigned to ships, sea areas, routes, or maritime activities to define their status, function, or regulatory conditions.
-
E.
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.
- 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_69d7bdf69bc48190af6c2621f28ca351 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:38 p.m.