Triple
T7810540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lostock Hall |
E180668
|
entity |
| Predicate | distanceToPrestonCityCentre |
P34348
|
FINISHED |
| Object | approximately 3 miles south |
—
|
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 miles south | Statement: [Lostock Hall, distanceToPrestonCityCentre, approximately 3 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToPrestonCityCentre Context triple: [Lostock Hall, distanceToPrestonCityCentre, approximately 3 miles south]
-
A.
distanceToPreston
chosen
Indicates the spatial distance between a given entity and the location named Preston.
-
B.
distanceToBradfordCityCentre
Indicates the spatial distance between a given location and the centre of Bradford city.
-
C.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
-
D.
directionFromCityCentre
Indicates the compass direction in which one location lies relative to the city centre.
-
E.
distanceToChesterCityCentre
Indicates the measured or specified distance between a given location and the centre of Chester city.
- 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_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. |
Created at: March 30, 2026, 4:37 p.m.