Triple
T34241335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clementi, Singapore |
E878473
|
entity |
| Predicate | servedByBusInterchange |
P2423
|
FINISHED |
| Object | Clementi Bus Interchange |
—
|
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: Clementi Bus Interchange | Statement: [Clementi, Singapore, servedByBusInterchange, Clementi Bus Interchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByBusInterchange Context triple: [Clementi, Singapore, servedByBusInterchange, Clementi Bus Interchange]
-
A.
hasBusInterchange
chosen
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
B.
connectsToBusAt
Indicates that one entity has an access or transfer point where it links to a bus service at a specific location or stop.
-
C.
accessByBusFrom
Indicates that one location can be reached from another location using a bus as the mode of transportation.
-
D.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
-
E.
isMainBusStationFor
Indicates that one bus station serves as the primary or central station for a particular area, network, or service.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
Created at: May 1, 2026, 1:56 a.m.