Triple
T9664508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aberystwyth railway station |
E233667
|
entity |
| Predicate | distanceFromShrewsbury |
P59110
|
FINISHED |
| Object | approximately 81 miles by rail |
—
|
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 81 miles by rail | Statement: [Aberystwyth railway station, distanceFromShrewsbury, approximately 81 miles by rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromShrewsbury Context triple: [Aberystwyth railway station, distanceFromShrewsbury, approximately 81 miles by rail]
-
A.
distanceToShrewsbury
chosen
Indicates the measured distance between a given entity or location and the town of Shrewsbury.
-
B.
distanceFromRothbury
Indicates the spatial distance between a given entity or location and Rothbury.
-
C.
distanceToBridgwater
Indicates the spatial distance between a given entity and the location named Bridgwater.
-
D.
distanceToOswestry
Indicates the spatial distance between a given entity and the location of Oswestry.
-
E.
distanceToWymondham
Indicates the spatial distance between a given entity or location and Wymondham.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0e1ef481909c50a4ba5fd94583 |
completed | April 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:14 p.m.