Triple
T7811208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramsgreave and Wilpshire railway station |
E180687
|
entity |
| Predicate | distanceFromBlackburn |
P79143
|
FINISHED |
| Object | approximately 3 km 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 3 km north | Statement: [Ramsgreave and Wilpshire railway station, distanceFromBlackburn, approximately 3 km north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBlackburn Context triple: [Ramsgreave and Wilpshire railway station, distanceFromBlackburn, approximately 3 km north]
-
A.
distanceFromBolton
Indicates the spatial distance between a given entity or location and the place named Bolton.
-
B.
distanceToBirmingham
Indicates the spatial distance between a given entity’s location and the city of Birmingham.
-
C.
distanceToLondon
Indicates the measured distance between a given entity’s location and the city of London.
-
D.
distanceToManchester
Indicates the measured or calculated distance between a given entity’s location and the city of Manchester.
-
E.
distanceToBradfordCityCentre
Indicates the spatial distance between a given location and the centre of Bradford city.
- F. None of above. chosen
Provenance (4 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_69ca827f6f148190beca4e245b993506 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78cd1cc8190b4cdd9850e1e2bb7 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:37 p.m.