Triple
T19923450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albrighton railway station |
E478858
|
entity |
| Predicate | distanceFromWolverhampton |
P59406
|
FINISHED |
| Object | approximately 9 miles |
—
|
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 9 miles | Statement: [Albrighton railway station, distanceFromWolverhampton, approximately 9 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromWolverhampton Context triple: [Albrighton railway station, distanceFromWolverhampton, approximately 9 miles]
-
A.
distanceToWolverhampton
chosen
Indicates the measured distance between a given location or entity and the place Wolverhampton.
-
B.
distanceToBirmingham
Indicates the spatial distance between a given entity’s location and the city of Birmingham.
-
C.
distanceFromWiganNorthWestern
Indicates the spatial distance between a given location and Wigan North Western station.
-
D.
distanceFromBolton
Indicates the spatial distance between a given entity or location and the place named Bolton.
-
E.
distanceToCoventry
Indicates the measured or specified distance between a given entity’s location and the city of Coventry.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c7be948190a65a1c78ba68dff3 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.