Triple
T26791844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodlands North MRT station |
E670537
|
entity |
| Predicate | isBorderAccessPoint |
P162179
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Woodlands North MRT station, isBorderAccessPoint, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBorderAccessPoint Context triple: [Woodlands North MRT station, isBorderAccessPoint, yes]
-
A.
isAccessPointOf
Indicates that one entity serves as an access point or entry interface through which another entity can be reached, used, or connected to.
-
B.
typeOfAccessPoint
Indicates the specific kind or category of access point involved in the relationship or action.
-
C.
hasAccessPointFrom
Indicates that an entity can be reached or entered from a specific access point.
-
D.
isMajorAccessPointFor
Indicates that something serves as a primary or significant entry or connection point for accessing another entity or system.
-
E.
hasModernAccessPoint
Indicates that one entity provides or includes a contemporary means or facility through which another entity can be accessed or used.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 4:17 a.m.