Triple

T22118328
Position Surface form Disambiguated ID Type / Status
Subject City Hall MRT station E546596 entity
Predicate hasPassengerServiceCentre P38302 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: [City Hall MRT station, hasPassengerServiceCentre, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPassengerServiceCentre
Context triple: [City Hall MRT station, hasPassengerServiceCentre, yes]
  • A. hasPassengerServicesTo
    Indicates that a transportation provider operates passenger services connecting one location or entity to another.
  • B. hasPassengerTerminal
    Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
  • C. hasPassengerTerminalFacilities chosen
    Indicates that an entity provides facilities or infrastructure specifically intended for handling and serving passengers.
  • D. hasPassengerTerminalFunction
    Indicates that something serves the role or performs the function of a passenger terminal, supporting the handling and movement of passengers.
  • E. isPrimaryPassengerHubOf
    Indicates that a location serves as the main passenger transportation hub for a particular carrier, network, or region.
  • 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_69e11e38b3848190ac3a4fa97d56e65a completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1294fcf2c81909b610e03a0f1921f completed April 28, 2026, 9:40 p.m.
PD Predicate disambiguation batch_69e71b2ed7348190b6fa2e52f54393fb completed April 21, 2026, 6:37 a.m.
Created at: April 16, 2026, 8:31 p.m.