Triple

T29431820
Position Surface form Disambiguated ID Type / Status
Subject Fauntleroy–Vashon–Southworth ferry route E746451 entity
Predicate connectsMainland P195131 FINISHED
Object Seattle NE NERFINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Seattle | Statement: [Fauntleroy–Vashon–Southworth ferry route, connectsMainland, Seattle]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsMainland
Context triple: [Fauntleroy–Vashon–Southworth ferry route, connectsMainland, Seattle]
  • A. mainlandConnection
    Indicates that there is a direct physical or infrastructural link between an area (often an island or remote region) and a mainland territory.
  • B. connectedToMainlandBy
    Indicates that one landmass or area is physically linked to a mainland, typically via a bridge, causeway, or other continuous connection.
  • C. connectsSpecialAdministrativeRegion
    Indicates a relationship where one entity is linked or associated specifically with a special administrative region.
  • D. terminalOnMainland
    Indicates that a transportation or service terminal is physically located on the mainland rather than on an island or offshore location.
  • E. connectsInlandRoutesTo
    Indicates that one entity serves as a link or junction that enables inland transportation routes to reach or connect with another entity.
  • F. None of above. chosen

Provenance (4 batches)

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_69f0a7a06e0081908add494075912eb4 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69fda94697c4819081291967202248be completed May 8, 2026, 9:13 a.m.
PD Predicate disambiguation batch_69fda5973fcc8190a57daef31fb70a49 completed May 8, 2026, 8:57 a.m.
PDg Predicate description generation batch_69fda945e1e08190bf923fcd4d2c548a completed May 8, 2026, 9:13 a.m.
Created at: April 28, 2026, 3:13 p.m.