Triple

T30719306
Position Surface form Disambiguated ID Type / Status
Subject Expo Line phase 1 E782106 entity
Predicate reusedCorridor P61930 FINISHED
Object former freight rail corridor along Exposition Boulevard LITERAL FINISHED

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: former freight rail corridor along Exposition Boulevard | Statement: [Expo Line phase 1, reusedCorridor, former freight rail corridor along Exposition Boulevard]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reusedCorridor
Context triple: [Expo Line phase 1, reusedCorridor, former freight rail corridor along Exposition Boulevard]
  • A. replacedInCorridorBy
    Indicates that one entity has been substituted or superseded by another entity specifically within a corridor context.
  • B. formerUseOfCorridor chosen
    Indicates that a corridor was previously used for a particular purpose or function, but is no longer used in that way.
  • C. inCorridor
    Indicates that one entity is located within or inside a corridor relative to another spatial context or reference.
  • D. otherMainCorridor
    Indicates that one corridor is an alternative or secondary main corridor relative to another within the same structure or network.
  • E. hasCorridor
    Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
  • 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_69f224acd24481908ed5f96f0d69b5dd completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f68c583438819093b812f11327eb60 completed May 2, 2026, 11:44 p.m.
PD Predicate disambiguation batch_69f6861170d08190bb98be609d436f84 completed May 2, 2026, 11:17 p.m.
Created at: April 29, 2026, 8:36 p.m.