Triple
T18955759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holmes Chapel railway station |
E463774
|
entity |
| Predicate | distanceFromCrewe |
P62214
|
FINISHED |
| Object | approximately 10 miles north |
—
|
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 10 miles north | Statement: [Holmes Chapel railway station, distanceFromCrewe, approximately 10 miles north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromCrewe Context triple: [Holmes Chapel railway station, distanceFromCrewe, approximately 10 miles north]
-
A.
distanceToCrewe
chosen
Indicates the spatial distance between an entity and the location Crewe.
-
B.
distanceToStokeOnTrent
Indicates the measured distance between a given entity’s location and the location of Stoke-on-Trent.
-
C.
distanceToLiverpoolCentral
Indicates the spatial distance between a given location and Liverpool Central.
-
D.
distanceFromBolton
Indicates the spatial distance between a given entity or location and the place named Bolton.
-
E.
distanceFromTamworth
Indicates the spatial distance measured from the reference location Tamworth to another place or entity.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d546babc81909d4fc5b6b4441aac |
completed | April 20, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon