Triple
T9301612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gatley railway station |
E223775
|
entity |
| Predicate | distanceFromManchesterPiccadilly |
P13107
|
FINISHED |
| Object | approximately 6.5 miles |
—
|
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: approximately 6.5 miles | Statement: [Gatley railway station, distanceFromManchesterPiccadilly, approximately 6.5 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromManchesterPiccadilly Context triple: [Gatley railway station, distanceFromManchesterPiccadilly, approximately 6.5 miles]
-
A.
distanceToManchester
chosen
Indicates the measured or calculated distance between a given entity’s location and the city of Manchester.
-
B.
distanceToManchesterAirport
Indicates the spatial distance between a given location or entity and Manchester Airport.
-
C.
distanceFromLiverpoolLimeStreet
Indicates the spatial distance between a given location and Liverpool Lime Street station.
-
D.
distanceToYorkCityCentre
Indicates the measured or specified distance between a given location and the centre of York city.
-
E.
distanceFromLiverpoolCityCentre
Indicates the spatial distance between a given location and the center of Liverpool city.
- 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.