Triple

T29105051
Position Surface form Disambiguated ID Type / Status
Subject Fauntleroy ferry terminal E736739 entity
Predicate instanceOf P0 FINISHED
Object Washington State Ferries terminal C6402 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: Washington State Ferries terminal
Context triple: [Fauntleroy ferry terminal, instanceOf, Washington State Ferries terminal]
  • A. bridge in Seattle
    A bridge in Seattle is a structural crossing—often spanning water or valleys—that connects different parts of the city or region, accommodating vehicles, pedestrians, and sometimes rail while withstanding the Pacific Northwest’s climate and seismic conditions.
  • B. ferry terminal chosen
    A ferry terminal is a designated facility where passengers and vehicles embark and disembark from ferries, typically providing ticketing, waiting areas, and docking infrastructure.
  • C. arm of Puget Sound
    An arm of Puget Sound is a smaller, branching inlet or extension of the main Puget Sound waterway, typically characterized by narrower channels that reach inland and connect to bays, coves, or river mouths.
  • D. Alaska Marine Highway route
    An Alaska Marine Highway route is a designated ferry corridor within the Alaska Marine Highway System that connects specific coastal communities and ports according to a defined schedule and service pattern.
  • E. river pier
    A river pier is a fixed or floating structure extending from the riverbank into the water, used for mooring boats, loading and unloading goods or passengers, and providing access to the river.
  • 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_69f077ec765c81909474c88bcc8bab43 completed April 28, 2026, 9:03 a.m.
Created at: April 28, 2026, 11:15 a.m.