Triple
T26686054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuas Expressway |
E672746
|
entity |
| Predicate | hasWesternTerminus |
P51120
|
FINISHED |
| Object | Tuas Checkpoint |
—
|
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: Tuas Checkpoint | Statement: [Tuas Expressway, hasWesternTerminus, Tuas Checkpoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWesternTerminus Context triple: [Tuas Expressway, hasWesternTerminus, Tuas Checkpoint]
-
A.
hasTerminusWest
chosen
Indicates that something has its western endpoint, terminus, or final stop at the referenced entity.
-
B.
westernTerminusDetail
Indicates the specific endpoint location or characteristics associated with the western terminus of a route or linear feature.
-
C.
terminusProvinceWest
Indicates that the western terminus of an entity (such as a route or line) is located within a specified province.
-
D.
westernTerminusNear
Indicates that the western endpoint of one entity is located close to another entity.
-
E.
hasSouthernTerminus
Indicates that one entity serves as the southern endpoint or terminus of another entity, such as a route, line, or path.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6173e191481909d1f6691a6fa8396 |
completed | May 2, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:23 a.m.