Triple
T5841519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hathersage railway station |
E129604
|
entity |
| Predicate | distanceFromSheffield |
P61201
|
FINISHED |
| Object | approximately 10 miles west |
—
|
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 west | Statement: [Hathersage railway station, distanceFromSheffield, approximately 10 miles west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSheffield Context triple: [Hathersage railway station, distanceFromSheffield, approximately 10 miles west]
-
A.
distanceToSheffieldCityCentre
chosen
Indicates the spatial distance between a given location and the centre of Sheffield city.
-
B.
distanceFromLeeds
Indicates the spatial distance between a given entity and the location of Leeds.
-
C.
distanceToSalford
Indicates the spatial distance between a given entity and the location of Salford.
-
D.
distanceToHuddersfield
Indicates the spatial distance between a given entity or location and the town of Huddersfield.
-
E.
distanceToManchester
Indicates the measured or calculated distance between a given entity’s location and the city of Manchester.
- 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.