Triple
T37938649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Builth Road railway station |
E946418
|
entity |
| Predicate | distanceFromTownServed |
P200374
|
FINISHED |
| Object | approximately 2 miles north of Builth Wells |
—
|
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 2 miles north of Builth Wells | Statement: [Builth Road railway station, distanceFromTownServed, approximately 2 miles north of Builth Wells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTownServed Context triple: [Builth Road railway station, distanceFromTownServed, approximately 2 miles north of Builth Wells]
-
A.
nearbyCityServed
Indicates that a city is geographically close enough to another city to be considered within its service or support area.
-
B.
nearestTownDistance
Indicates the distance from a given location to the closest town.
-
C.
approximateDistanceFromTownCentre
chosen
Indicates the estimated spatial distance between a given location and the center of a town.
-
D.
townServed
Indicates that a given service, facility, or infrastructure serves or provides coverage to a particular town.
-
E.
distanceFromHanaTown (miles)
Indicates the number of miles separating a given place or entity from Hana Town.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.