Triple
T25195772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morden Hall Park |
E630994
|
entity |
| Predicate | nearestTramStop |
P29999
|
FINISHED |
| Object | Morden Road tram stop |
—
|
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: Morden Road tram stop | Statement: [Morden Hall Park, nearestTramStop, Morden Road tram stop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestTramStop Context triple: [Morden Hall Park, nearestTramStop, Morden Road tram stop]
-
A.
hasNearbyTramStop
chosen
Indicates that a location has a tram stop situated within a short walking distance or close proximity.
-
B.
nearestRailwayTerminus
Indicates that one location is the closest railway terminus to another specified place.
-
C.
nearbyTerminus
Indicates that one terminus (end point or final stop) is located close to another terminus in space.
-
D.
nearestMajorTransportHub
Indicates that one location is the closest significant transportation center (such as a major train station, airport, or bus terminal) to another location.
-
E.
nearestEntranceStation
Indicates that one station is the closest entrance station to a given location or entity compared to all other candidate stations.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 21, 2026, 12:46 p.m.