Triple
T30848645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barkingside tube station |
E785713
|
entity |
| Predicate | liesBetweenStationsOnCentralLine |
P66204
|
FINISHED |
| Object | Newbury Park |
—
|
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: Newbury Park | Statement: [Barkingside tube station, liesBetweenStationsOnCentralLine, Newbury Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesBetweenStationsOnCentralLine Context triple: [Barkingside tube station, liesBetweenStationsOnCentralLine, Newbury Park]
-
A.
isBetweenStationsOnLine
chosen
Indicates that something is located or occurs between two stations along the same transit line.
-
B.
hasAdjacentStationOnCentralLine
Indicates that one station is directly next to another station along the Central Line.
-
C.
hasBakerlooPlatformsBetween
Indicates that there are Bakerloo line platforms located between two specified points or stations.
-
D.
isAdjacentStationOnJubileeLine
Indicates that two stations are directly next to each other as consecutive stops on the Jubilee Line.
-
E.
isAdjacentStationOnPiccadillyLine
Indicates that two stations are directly next to each other as consecutive stops on the Piccadilly Line.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6917a847481909d9339914f9c89e5 |
completed | May 3, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:46 p.m.