Triple
T36404827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanjung Malim |
E896722
|
entity |
| Predicate | isNearExpressway |
P117140
|
FINISHED |
| Object | North–South Expressway Northern Route |
—
|
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: North–South Expressway Northern Route | Statement: [Tanjung Malim, isNearExpressway, North–South Expressway Northern Route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNearExpressway Context triple: [Tanjung Malim, isNearExpressway, North–South Expressway Northern Route]
-
A.
isLocatedOnHighway
Indicates that one entity is situated along, adjacent to, or directly accessible from a specific highway.
-
B.
hasExpresswaySection
Indicates that an entity includes, contains, or is associated with a specific section or segment of an expressway.
-
C.
hasRoadProximity
chosen
Indicates that one entity is located near or adjacent to a road in terms of spatial proximity.
-
D.
isOnOrbitalMotorway
Indicates that one entity (typically a route or segment) lies on or forms part of an orbital motorway that encircles a city or area.
-
E.
approximateDistanceFromHighway1
Indicates the estimated distance between a location and Highway 1, rather than an exact measured value.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.