Triple
T32252875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Diego Unified Port District Act |
E823928
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | port district enabling statute |
C14237
|
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: port district enabling statute Context triple: [San Diego Unified Port District Act, instanceOf, port district enabling statute]
-
A.
port governance legislation
chosen
Port governance legislation comprises the legal frameworks and regulatory instruments that define the ownership, management structures, operational rules, and oversight mechanisms for the administration and development of seaports.
-
B.
statutory harbour authority
A statutory harbour authority is a legally established body empowered by specific legislation to manage, regulate, and develop a designated harbour or port area, including its navigation, safety, and related infrastructure.
-
C.
municipal enabling act
A municipal enabling act is a statute passed by a higher level of government that grants municipalities the legal authority and powers necessary to govern and regulate local affairs.
-
D.
naval district
A naval district is a geographically defined administrative area of a navy responsible for organizing, supporting, and overseeing naval operations, personnel, and facilities within its boundaries.
-
E.
port area
A port area is a designated coastal or riverside zone equipped with infrastructure and facilities for the berthing, loading, unloading, storage, and transfer of cargo and passengers between land and water transport.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:41 a.m.