Triple

T35040035
Position Surface form Disambiguated ID Type / Status
Subject Setia Jaya KTM station via BRT E1011043 entity
Predicate hasPlatformConnectionType P62886 FINISHED
Object off-street transfer 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: off-street transfer | Statement: [Setia Jaya KTM station via BRT, hasPlatformConnectionType, off-street transfer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPlatformConnectionType
Context triple: [Setia Jaya KTM station via BRT, hasPlatformConnectionType, off-street transfer]
  • A. hasPlatformsConnectedBy
    Indicates that two or more platforms are linked together by some connecting structure or mechanism.
  • B. hasPlatformType
    Indicates that an entity is associated with or characterized by a specific type or category of platform.
  • C. hasNoConnectionType
    Indicates that there is explicitly no defined type or category of connection between the related entities.
  • D. hasSurfaceConnection
    Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity between them.
  • E. hasModeConnection chosen
    Indicates a relationship where one entity is linked to another through a specific mode, method, or type of connection.
  • 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_69f76dcea02c81908542a223f6d5059f completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fd6dbd1b648190b1a0b391c03aebc5 completed May 8, 2026, 4:59 a.m.
PD Predicate disambiguation batch_69fd6a9020548190bbfa845360ac85fb completed May 8, 2026, 4:46 a.m.
Created at: May 3, 2026, 4:01 p.m.