Triple

T37036700
Position Surface form Disambiguated ID Type / Status
Subject Semantan station E916659 entity
Predicate hasFeederBusServices P39381 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: [Semantan station, hasFeederBusServices, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFeederBusServices
Context triple: [Semantan station, hasFeederBusServices, yes]
  • A. hasBusServices chosen
    Indicates that one location or entity is served by bus routes or bus transportation provided by another.
  • B. hasCommuterServices
    Indicates that a location or facility provides transportation services specifically intended for regular commuters, such as daily or frequent travelers between home and work or school.
  • C. hasNightBusService
    Indicates that a transportation route or stop is served by buses operating during nighttime hours.
  • D. hasBusRapidTransitFeatures
    Indicates that a transportation route or corridor includes design or operational elements characteristic of bus rapid transit systems.
  • E. hasSuburbanService
    Indicates that an entity provides or is connected to a public transportation service specifically serving suburban areas, typically linking suburbs with urban centers.
  • 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_69f76e93ec4c8190be81cf87354d9155 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fd09840ea88190a2e6d7e577ade717 completed May 7, 2026, 9:52 p.m.
PD Predicate disambiguation batch_69fd064c49988190afadddbd04d7cb94 completed May 7, 2026, 9:38 p.m.
Created at: May 3, 2026, 4:14 p.m.