Triple
T20526955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Board of Port Commissioners of the Port of Redwood City |
E503962
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | port governing body |
C172
|
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 governing body Context triple: [Board of Port Commissioners of the Port of Redwood City, instanceOf, port governing body]
-
A.
port authority
A port authority is an organization responsible for managing, regulating, and developing a seaport or group of ports, including their infrastructure, operations, and related maritime activities.
-
B.
port governance legislation
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.
-
C.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
D.
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.
-
E.
port industry association
A port industry association is an organized body that represents and coordinates the interests, standards, and collaborative initiatives of ports and related maritime stakeholders within a region or sector.
- 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:37 a.m.