Triple
T30400862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vice-Admiral of the Coast of Northumberland |
E773343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime administrative office |
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 administrative office Context triple: [Vice-Admiral of the Coast of Northumberland, instanceOf, maritime administrative office]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
naval office
A naval office is an administrative entity within a navy responsible for managing operations, logistics, personnel, and documentation related to maritime military activities.
-
E.
harbormaster office
A harbormaster office is the administrative and operational center at a port or marina responsible for coordinating vessel movements, enforcing harbor regulations, and managing maritime safety and 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:03 p.m.