Triple
T37093590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sungai Buloh station |
E918491
|
entity |
| Predicate | openedAsMRTStationOn |
P195215
|
FINISHED |
| Object | 16 December 2016 |
—
|
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: 16 December 2016 | Statement: [Sungai Buloh station, openedAsMRTStationOn, 16 December 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsMRTStationOn Context triple: [Sungai Buloh station, openedAsMRTStationOn, 16 December 2016]
-
A.
openedAsBMTStation
Indicates that an entity first began operation or service specifically as a BMT (Brooklyn–Manhattan Transit) station.
-
B.
openedAsTransitStation
Indicates that an entity began operation specifically as a transit station at the time it was opened.
-
C.
openedAsRERStation
Indicates that a station began operation specifically as part of the RER (Réseau Express Régional) network from its opening date.
-
D.
openingDateToRapidTransit
Indicates the date on which a rapid transit service or connection was opened or became operational.
-
E.
openedAsMBTAStation
Indicates that an entity began operation specifically as an MBTA station at a particular time.
- F. None of above. chosen
Provenance (4 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69fdb04d37288190969a0f39d92efb49 |
completed | May 8, 2026, 9:43 a.m. |
Created at: May 3, 2026, 4:14 p.m.