Triple

T29682873
Position Surface form Disambiguated ID Type / Status
Subject Duke Point ferry terminal E751001 entity
Predicate isOnFerryRoute P110394 FINISHED
Object Nanaimo–Vancouver (via Tsawwassen) 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: Nanaimo–Vancouver (via Tsawwassen) | Statement: [Duke Point ferry terminal, isOnFerryRoute, Nanaimo–Vancouver (via Tsawwassen)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isOnFerryRoute
Context triple: [Duke Point ferry terminal, isOnFerryRoute, Nanaimo–Vancouver (via Tsawwassen)]
  • A. hasNearbyFerryRoute
    Indicates that there is a ferry route located close to the referenced entity.
  • B. isOneOfMainCarFerryRoutesTo chosen
    Indicates that something serves as one of the primary car ferry routes leading to a specified destination.
  • C. hasFerryService
    Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
  • D. hasFerryComponent
    Indicates that something includes or is associated with a ferry-related part, feature, or segment within its structure or operation.
  • E. hasFerryType
    Indicates that an entity (such as a ferry route or service) is associated with a specific type or category of ferry.
  • F. None of above.

Provenance (3 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_69f0d624d7b08190ba237d226f78d0d9 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f6728d8d8881909cc97dd523866934 completed May 2, 2026, 9:54 p.m.
PD Predicate disambiguation batch_69f6659f246081909821c5f452d14e8f completed May 2, 2026, 8:59 p.m.
Created at: April 28, 2026, 7:11 p.m.