Triple
T30981060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Gate Ferry connection at Sausalito |
E789373
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intermodal transport terminal |
C37500
|
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: intermodal transport terminal Context triple: [Golden Gate Ferry connection at Sausalito, instanceOf, intermodal transport terminal]
-
A.
intermodal passenger station
An intermodal passenger station is a transportation facility where travelers can conveniently transfer between multiple modes of passenger transport, such as trains, buses, trams, and sometimes air or ferry services, within a coordinated hub.
-
B.
maritime cargo terminal
A maritime cargo terminal is a specialized facility at a seaport where ships are loaded and unloaded, and cargo is temporarily stored, sorted, and transferred between sea and land transportation modes.
-
C.
transport terminal
chosen
A transport terminal is a designated facility where passengers or goods begin, end, or transfer between different modes or routes of transportation.
-
D.
cross-border terminal
A cross-border terminal is a transportation facility located at or near an international boundary that consolidates, processes, and transfers passengers or freight between different countries’ transport networks while handling customs, immigration, and regulatory controls.
-
E.
bulk cargo terminal
A bulk cargo terminal is a specialized port facility designed for the efficient handling, storage, and transfer of unpackaged bulk commodities such as coal, grain, ore, and fertilizers between ships, land transport, and storage areas.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:55 p.m.