Triple

T14686525
Position Surface form Disambiguated ID Type / Status
Subject Revesby railway station E344920 entity
Predicate hasKissAndRideZone P33499 FINISHED
Object yes 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: yes | Statement: [Revesby railway station, hasKissAndRideZone, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasKissAndRideZone
Context triple: [Revesby railway station, hasKissAndRideZone, yes]
  • A. hasKissAndRide chosen
    Indicates that a location provides a designated area where passengers can be briefly dropped off or picked up, typically by car, without long-term parking.
  • B. hasParkAndRideFunction
    Indicates that a location or facility serves as a park-and-ride, where people can park vehicles and transfer to another mode of transport for the rest of their journey.
  • C. fareZoneIncludes
    Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
  • D. hasValleyAccessTo
    Indicates that one location can be reached from another specifically by traveling through a valley or valley-based route.
  • E. hasParkAndRideGarage
    Indicates that a location includes a parking facility where people can park their vehicles and transfer to public transit services.
  • 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_69d822e34b348190ada4d1cdb6c7c226 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb58306548190b981956a83a84b95 completed April 14, 2026, 9:45 p.m.
PD Predicate disambiguation batch_69de6579fb7881909becc8f5822b39d4 completed April 14, 2026, 4:04 p.m.
Created at: April 10, 2026, 1:28 a.m.