Triple
T24999991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mouldsworth railway station |
E625690
|
entity |
| Predicate | distanceToChesterApprox |
P29987
|
FINISHED |
| Object | about 8 miles northeast of Chester |
—
|
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: about 8 miles northeast of Chester | Statement: [Mouldsworth railway station, distanceToChesterApprox, about 8 miles northeast of Chester]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToChesterApprox Context triple: [Mouldsworth railway station, distanceToChesterApprox, about 8 miles northeast of Chester]
-
A.
distanceToChesterCityCentre
chosen
Indicates the measured or specified distance between a given location and the centre of Chester city.
-
B.
distanceToChesterfield
Indicates the spatial distance between a given entity and the location named Chesterfield.
-
C.
distanceToChichester
Indicates the measured distance between a given location or entity and the place Chichester.
-
D.
distanceToChepstow
Indicates the spatial distance between a given entity and the location of Chepstow.
-
E.
distanceToCheltenham
Indicates the spatial distance between a given entity and the location of Cheltenham.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 18, 2026, 6:04 a.m.