Triple

T25847783
Position Surface form Disambiguated ID Type / Status
Subject Quebec City–Montreal line E651119 entity
Predicate hasPassengerServiceBrand P171390 FINISHED
Object Via Rail Corridor 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: Via Rail Corridor | Statement: [Quebec City–Montreal line, hasPassengerServiceBrand, Via Rail Corridor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPassengerServiceBrand
Context triple: [Quebec City–Montreal line, hasPassengerServiceBrand, Via Rail Corridor]
  • A. hasPassengerServicesTo
    Indicates that a transportation provider operates passenger services connecting one location or entity to another.
  • B. hasPassengerOnlyService
    Indicates that the service provided involves only the transportation of passengers, with no freight or cargo component.
  • C. hasPassengerAirlineService
    Indicates that a location or facility is served by scheduled passenger airline flights.
  • D. isInPassengerService
    Indicates that an entity (such as a vehicle, vessel, or aircraft) is currently being used to carry passengers as part of regular service.
  • E. hasPassengerAmenity
    Indicates that an entity provides or is equipped with a specific amenity intended for the comfort or convenience of its passengers.
  • 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_69e7ab39035c8190be15c8aaee1bb858 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f69f80b62c8190bf2af2be0d3a7df8 completed May 3, 2026, 1:06 a.m.
PD Predicate disambiguation batch_69f69d17e8d48190b30bcc2f4bd81eb2 completed May 3, 2026, 12:55 a.m.
PDg Predicate description generation batch_69f69edae2448190925ce701c8792c52 completed May 3, 2026, 1:03 a.m.
Created at: April 22, 2026, 7:57 a.m.