Triple

T5568545
Position Surface form Disambiguated ID Type / Status
Subject Circular Quay railway station E145938 entity
Predicate hasIntermodalConnection P2423 FINISHED
Object bus 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: bus | Statement: [Circular Quay railway station, hasIntermodalConnection, bus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasIntermodalConnection
Context triple: [Circular Quay railway station, hasIntermodalConnection, bus]
  • A. hasBusInterchange chosen
    Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
  • B. hasLandsideConnection
    Indicates that two locations are connected by a route or access on land, allowing movement between them without using air or water transport.
  • C. hasAirsideConnection
    Indicates that there is a direct, secure connection between areas past security (airside) of two locations, allowing passengers to transfer without re-clearing security or immigration.
  • D. isTransportHubBetween
    Indicates that a location functions as a central node facilitating transportation connections between two or more other places.
  • E. hasIntermediateStation
    Indicates that a route, journey, or connection includes a station that lies between its starting point and its final destination.
  • 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_69c008fdae24819081aa002ad99cd966 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c0203789688190a0bab723186214ad completed March 22, 2026, 5 p.m.
PD Predicate disambiguation batch_69c01b12826c8190969a584d0f53aa44 completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:36 p.m.