Triple
T9301613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gatley railway station |
E223775
|
entity |
| Predicate | directionFromManchesterPiccadilly |
P12100
|
FINISHED |
| Object | south |
—
|
LITERAL FINISHED |
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 | Statement: [Gatley railway station, directionFromManchesterPiccadilly, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromManchesterPiccadilly Context triple: [Gatley railway station, directionFromManchesterPiccadilly, south]
-
A.
directionFromManchesterCityCentre
chosen
Indicates the compass direction in which one location lies when measured outward from Manchester city centre.
-
B.
primaryManchesterStation
Indicates that a given station is the main or principal railway station serving Manchester.
-
C.
adjacentStopDirectionManchester
Indicates that one stop is directly next to another in the specified travel direction toward Manchester.
-
D.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08d1d954819098be177addafa406 |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.