Triple
T35040018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Setia Jaya KTM station via BRT |
E1011043
|
entity |
| Predicate | adjacentToRailStation |
P30238
|
FINISHED |
| Object | Setia Jaya KTM station |
—
|
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: Setia Jaya KTM station | Statement: [Setia Jaya KTM station via BRT, adjacentToRailStation, Setia Jaya KTM station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentToRailStation Context triple: [Setia Jaya KTM station via BRT, adjacentToRailStation, Setia Jaya KTM station]
-
A.
adjacentToStation
chosen
Indicates that one entity is located next to or immediately beside a station.
-
B.
hasNearbyRailwayStation
Indicates that a railway station is located within a short or convenient distance from the referenced entity.
-
C.
hasAdjacentNationalRailStation
Indicates that one location has a national rail station situated directly next to or immediately beside it.
-
D.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
E.
hasNearbyRailway
Indicates that one entity is located close to a railway associated with or relevant to another entity.
- 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_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:01 p.m.