Triple
T19429907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falmouth Harbormaster |
E486083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government maritime authority |
C15097
|
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: local government maritime authority Context triple: [Falmouth Harbormaster, instanceOf, local government maritime authority]
-
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
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.
local governmental entity
chosen
A local governmental entity is an administrative organization, such as a city, county, or district, that exercises governmental authority and provides public services within a specific geographic area below the level of the central or national government.
-
D.
maritime law enforcement unit
A maritime law enforcement unit is an organized body responsible for enforcing laws, ensuring security, and protecting resources within a nation’s territorial waters and maritime zones.
-
E.
maritime law enforcement activity
Maritime law enforcement activity is the set of actions by authorized agencies to monitor, control, and ensure compliance with laws and regulations in maritime zones, including preventing and responding to illegal activities at sea.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:37 p.m.