Triple
T24999992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mouldsworth railway station |
E625690
|
entity |
| Predicate | distanceToManchesterApprox |
P13107
|
FINISHED |
| Object | about 30 miles southwest of Manchester |
—
|
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 30 miles southwest of Manchester | Statement: [Mouldsworth railway station, distanceToManchesterApprox, about 30 miles southwest of Manchester]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToManchesterApprox Context triple: [Mouldsworth railway station, distanceToManchesterApprox, about 30 miles southwest of Manchester]
-
A.
distanceToManchester
chosen
Indicates the measured or calculated distance between a given entity’s location and the city of Manchester.
-
B.
distanceToManchesterAirport
Indicates the spatial distance between a given location or entity and Manchester Airport.
-
C.
distanceToSalford
Indicates the spatial distance between a given entity and the location of Salford.
-
D.
distanceFromManchesterVictoria
Indicates the measured distance between a given place or entity and Manchester Victoria.
-
E.
distanceToLondon
Indicates the measured distance between a given entity’s location and the city of London.
- 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_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 18, 2026, 6:04 a.m.