Triple
T25603969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Ruislip |
E641858
|
entity |
| Predicate | hasAdjacentNationalRailStation |
P163020
|
FINISHED |
| Object | South Ruislip |
—
|
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: South Ruislip | Statement: [West Ruislip, hasAdjacentNationalRailStation, South Ruislip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentNationalRailStation Context triple: [West Ruislip, hasAdjacentNationalRailStation, South Ruislip]
-
A.
hasAdjacentStationTowardsCentralLondon
Indicates that one station has a neighboring station located in the direction of central London along a transit route.
-
B.
adjacentToStation
Indicates that one entity is located next to or immediately beside a station.
-
C.
hasAdjacentBusStation
Indicates that one location has a bus station situated directly next to or very near it.
-
D.
hasAdjacentStationOnElizabethLine
Indicates that one station is directly next to another station along the Elizabeth Line, with no other stations in between.
-
E.
hasNearbyRailwayStation
Indicates that a railway station is located within a short or convenient distance from the referenced entity.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 21, 2026, 4:37 p.m.