Triple
T20963670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirkby Stephen railway station |
E516311
|
entity |
| Predicate | distanceFromCarlisle |
P24133
|
FINISHED |
| Object | approximately 41 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 41 miles | Statement: [Kirkby Stephen railway station, distanceFromCarlisle, approximately 41 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromCarlisle Context triple: [Kirkby Stephen railway station, distanceFromCarlisle, approximately 41 miles]
-
A.
distanceToCarlisle
chosen
Indicates the spatial distance between a given entity or location and Carlisle.
-
B.
directionFromCarlisle
Indicates the compass direction or relative bearing of one location when measured starting from Carlisle.
-
C.
distanceFromEnniskillen
Indicates the spatial distance between a given entity and the location of Enniskillen.
-
D.
distanceToClitheroe
Indicates the spatial distance between a given entity or location and the town of Clitheroe.
-
E.
distanceFromDurhamCity
Indicates the measured distance between an entity’s location and the city of Durham.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb710d6c8190a2daacaad3b22683 |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:32 p.m.