Triple
T36863890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Ruislip station |
E911017
|
entity |
| Predicate | adjacentNationalRailStation |
P163020
|
FINISHED |
| Object | South Ruislip station |
—
|
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 station | Statement: [West Ruislip station, adjacentNationalRailStation, South Ruislip station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentNationalRailStation Context triple: [West Ruislip station, adjacentNationalRailStation, South Ruislip station]
-
A.
hasAdjacentNationalRailStation
chosen
Indicates that one location has a national rail station situated directly next to or immediately beside it.
-
B.
adjacentToStation
Indicates that one entity is located next to or immediately beside a station.
-
C.
nearbyMajorStation
Indicates that one location is situated close to a major transportation station (such as a main train, bus, or metro hub).
-
D.
adjacentStationOnEastRailLine
Indicates that one station is directly next to another station along the eastbound direction of a rail line.
-
E.
hasAdjacentStationTowardsCentralLondon
Indicates that one station has a neighboring station located in the direction of central London along a transit route.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:13 p.m.