Triple
T20913767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapel-en-le-Frith railway station |
E515016
|
entity |
| Predicate | distanceFromBuxton |
P140899
|
FINISHED |
| Object | approximately 8 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 8 miles | Statement: [Chapel-en-le-Frith railway station, distanceFromBuxton, approximately 8 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBuxton Context triple: [Chapel-en-le-Frith railway station, distanceFromBuxton, approximately 8 miles]
-
A.
distanceToBuxton
chosen
Indicates the spatial distance between a given entity or location and the place named Buxton.
-
B.
distanceFromBolton
Indicates the spatial distance between a given entity or location and the place named Bolton.
-
C.
distanceToBodmin
Indicates the spatial distance between an entity and the location Bodmin.
-
D.
distanceToBurford
Indicates the spatial distance between a given entity or location and the place named Burford.
-
E.
distanceFromRothbury
Indicates the spatial distance between a given entity or location and Rothbury.
- 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_69e0b4f9d5ec8190bb2bd27350ed341c |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6ec60d3288190897a087bbdd4f005 |
completed | April 21, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:48 p.m.