Triple
T6522044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keynsham railway station |
E151206
|
entity |
| Predicate | distanceFromBristolTempleMeads |
P42445
|
FINISHED |
| Object | approximately 5 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 5 miles | Statement: [Keynsham railway station, distanceFromBristolTempleMeads, approximately 5 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBristolTempleMeads Context triple: [Keynsham railway station, distanceFromBristolTempleMeads, approximately 5 miles]
-
A.
distanceToBristol
chosen
Indicates the measured or calculated spatial distance between a given entity and the location of Bristol.
-
B.
directionFromBristol
Indicates the cardinal or relative compass direction of one place or object as measured outward starting from Bristol.
-
C.
distanceToBasingstoke
Indicates the spatial distance between a given entity and the location of Basingstoke.
-
D.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
E.
distanceToBradfordCityCentre
Indicates the spatial distance between a given location and the centre of Bradford 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad95c2c88190b800aaaa73f99210 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.