Triple
T35040031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Setia Jaya KTM station via BRT |
E1011043
|
entity |
| Predicate | operatorBRTComponent |
P51999
|
FINISHED |
| Object | Rapid Bus Sdn Bhd |
—
|
NE NERFINISHED |
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: Rapid Bus Sdn Bhd | Statement: [Setia Jaya KTM station via BRT, operatorBRTComponent, Rapid Bus Sdn Bhd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorBRTComponent Context triple: [Setia Jaya KTM station via BRT, operatorBRTComponent, Rapid Bus Sdn Bhd]
-
A.
openedAsBRT
Indicates that a transit service, corridor, or route was initially launched or began operation specifically as a bus rapid transit (BRT) system.
-
B.
hasBRTLine
Indicates that a bus rapid transit (BRT) line is present, operates on, or serves the referenced entity.
-
C.
temInfraestrutura
Indicates that one entity possesses, contains, or is equipped with the infrastructure provided or represented by another entity.
-
D.
operatorOfTransportInfrastructure
chosen
Indicates that an entity operates, manages, or runs a specific piece of transport infrastructure.
-
E.
tramOperator
Indicates that one entity operates, manages, or runs tram services for another entity or area.
- 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_6a01203ac018819085d7c9abd8345b23 |
completed | May 11, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_6a011f3f149c819090749722da0e3413 |
completed | May 11, 2026, 12:13 a.m. |
Created at: May 3, 2026, 4:01 p.m.