Triple

T30641151
Position Surface form Disambiguated ID Type / Status
Subject Roncesvalles Avenue E779981 entity
Predicate hasTransitRoute P34620 FINISHED
Object Toronto streetcar route 504 King 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: Toronto streetcar route 504 King | Statement: [Roncesvalles Avenue, hasTransitRoute, Toronto streetcar route 504 King]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTransitRoute
Context triple: [Roncesvalles Avenue, hasTransitRoute, Toronto streetcar route 504 King]
  • A. hasTransportRoute
    Indicates that there exists a designated transportation connection or route linking one entity to another.
  • B. hasPublicTransitRoute chosen
    Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving the related entities.
  • C. hasTransitAccessTo
    Indicates that one place or entity is reachable from another via public or shared transportation services.
  • D. hasTransitServiceType
    Indicates that a transit service is associated with a specific type or category of service (e.g., bus, rail, express).
  • E. isPublicTransportRoute
    Indicates that a given route is designated and operated as part of a public transportation system available for general use.
  • 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_69f224a50ebc81909b961a94c7f66b12 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fe8f74748c8190bd14a856c057f9f7 completed May 9, 2026, 1:35 a.m.
PD Predicate disambiguation batch_69fe8e7ed8088190929e0df67aca4de9 completed May 9, 2026, 1:31 a.m.
Created at: April 29, 2026, 8:29 p.m.