Triple
T26791813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodlands North MRT station |
E670537
|
entity |
| Predicate | lineStage |
P9657
|
FINISHED |
| Object | Thomson–East Coast Line Stage 1 |
—
|
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: Thomson–East Coast Line Stage 1 | Statement: [Woodlands North MRT station, lineStage, Thomson–East Coast Line Stage 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineStage Context triple: [Woodlands North MRT station, lineStage, Thomson–East Coast Line Stage 1]
-
A.
lineStandard
Indicates that one entity is a standard or reference specification that defines or governs the characteristics or requirements of a particular line (such as a product line, production line, or service line).
-
B.
lineUse
Indicates how a particular line (such as a route, track, or service line) is utilized or purposed within a system or network.
-
C.
lineStatus
Indicates the current operational or functional state of a line or connection within a system.
-
D.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
E.
stageOf
chosen
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f619bbe6a4819090598d7e100c2016 |
completed | May 2, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 4:16 a.m.