Triple
T35040038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Setia Jaya KTM station via BRT |
E1011043
|
entity |
| Predicate | BRTLineServed |
P37810
|
FINISHED |
| Object | BRT Sunway Line |
—
|
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: BRT Sunway Line | Statement: [Setia Jaya KTM station via BRT, BRTLineServed, BRT Sunway Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BRTLineServed Context triple: [Setia Jaya KTM station via BRT, BRTLineServed, BRT Sunway Line]
-
A.
hasBRTLine
chosen
Indicates that a bus rapid transit (BRT) line is present, operates on, or serves the referenced entity.
-
B.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
C.
railroadLineServed
Indicates that a particular railroad line provides service to, or operates through, a given location or facility.
-
D.
isPublicTransportBackboneOf
Indicates that one transport system serves as the primary structural and functional core of a region’s overall public transportation network.
-
E.
lightRailNetwork
Indicates a relationship where an area, city, or region is served by or contains a light rail transit network.
- 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_69f7859072cc8190b4801985dacff7e8 |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.