Triple
T26648922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodlands MRT station |
E668995
|
entity |
| Predicate | lineOpeningDate_NorthSouthLine |
P161084
|
FINISHED |
| Object | 10 February 1996 |
—
|
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: 10 February 1996 | Statement: [Woodlands MRT station, lineOpeningDate_NorthSouthLine, 10 February 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineOpeningDate_NorthSouthLine Context triple: [Woodlands MRT station, lineOpeningDate_NorthSouthLine, 10 February 1996]
-
A.
northLineExtensionOpeningDate
Indicates the date on which the extension of the North Line officially opened for service.
-
B.
line2OpeningDate
Indicates the date on which the second line (e.g., a route, service, or facility line) was officially opened or began operation.
-
C.
openedOnNorthernLinePredecessor
Indicates that something was opened on a railway line that preceded and was later replaced by the Northern line.
-
D.
lineSectionOpeningDate
Indicates the date on which a specific section of a line (e.g., a route, track, or corridor) was officially opened for use.
-
E.
blueLineOpeningDate
Indicates the date on which the Blue Line was officially opened or began operation.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f616778678819095bc601b19dbe0bd |
completed | May 2, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 2:32 a.m.