Triple
T13229688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRT Light Red Line |
E314977
|
entity |
| Predicate | futureExtensionPlan |
P19358
|
FINISHED |
| Object | extension further west from Taling Chan |
—
|
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: extension further west from Taling Chan | Statement: [MRT Light Red Line, futureExtensionPlan, extension further west from Taling Chan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureExtensionPlan Context triple: [MRT Light Red Line, futureExtensionPlan, extension further west from Taling Chan]
-
A.
plannedExtensionTo
Indicates that one entity is intended or scheduled to be extended, expanded, or continued by another entity in the future.
-
B.
plannedExpansion
Indicates that an entity has a scheduled or intended increase in size, capacity, scope, or presence in the future.
-
C.
plannedExtensionDirection
chosen
Indicates the intended directional path or orientation along which something is planned to be extended in the future.
-
D.
plannedExtensionLength
Indicates the intended or proposed length of an extension as specified in a plan or design.
-
E.
futureSiteOf
Indicates that a location is planned or designated to become the site of a particular entity or structure in the future.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d336ae08190bfc118cfbefddf84 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:21 p.m.