Triple
T34575583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bugis Junction |
E887742
|
entity |
| Predicate | MRTLineConnection |
P18378
|
FINISHED |
| Object | Downtown 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: Downtown Line | Statement: [Bugis Junction, MRTLineConnection, Downtown Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MRTLineConnection Context triple: [Bugis Junction, MRTLineConnection, Downtown Line]
-
A.
subwayLine
chosen
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
B.
railwayConnectsTo
Indicates that one railway line, track, or network is directly linked or joined to another, allowing trains to move between them.
-
C.
providesRailConnectionsWithin
Indicates that an entity offers or facilitates rail transport links connecting locations inside a specified area or region.
-
D.
monorailLines
Indicates that there is a monorail transit line or system associated with, serving, or present in the referenced entity.
-
E.
nearbyMainlineConnection
Indicates that one entity has a mainline connection located in close physical proximity 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720999db48190b89014e3ec01cb62 |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:03 a.m.