Triple

T34800672
Position Surface form Disambiguated ID Type / Status
Subject Vancouver–Calgary E1003209 entity
Predicate railCorridorIncludes P57554 FINISHED
Object Canadian Pacific Railway mainline 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: Canadian Pacific Railway mainline | Statement: [Vancouver–Calgary, railCorridorIncludes, Canadian Pacific Railway mainline]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railCorridorIncludes
Context triple: [Vancouver–Calgary, railCorridorIncludes, Canadian Pacific Railway mainline]
  • A. railCorridorType
    Indicates the specific classification or type of a rail corridor associated with the subject (e.g., mainline, branch line, high-speed, freight, etc.).
  • B. partOfRailwayCorridor chosen
    Indicates that one entity is a segment, component, or area belonging to or contained within a specific railway corridor.
  • C. servesRailCorridor
    Indicates that something (such as a service, facility, or operation) provides service to or operates along a specific rail corridor.
  • D. isRailwayIn
    Indicates that a railway is located within or passes through a specified geographic or administrative area.
  • E. railwayCorridorNumber
    Indicates the designated identification number assigned to a specific railway corridor within a rail network.
  • 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_69f76db543808190b188c6c86a91491b completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f7886be6d8819095ec62e4f2cee858 completed May 3, 2026, 5:39 p.m.
PD Predicate disambiguation batch_69f7841440f48190b4346c08855951d2 completed May 3, 2026, 5:21 p.m.
Created at: May 3, 2026, 3:59 p.m.