Triple
T32359996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilning railway station |
E826832
|
entity |
| Predicate | distanceFromSevernTunnelJunction |
P204268
|
FINISHED |
| Object | approximately 6 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 6 miles | Statement: [Pilning railway station, distanceFromSevernTunnelJunction, approximately 6 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSevernTunnelJunction Context triple: [Pilning railway station, distanceFromSevernTunnelJunction, approximately 6 miles]
-
A.
distanceToTrenton
Indicates the spatial distance between a given entity and the location identified as Trenton.
-
B.
distanceFromSettleJunction
Indicates the measured or specified distance between a given entity and the location identified as Settle Junction.
-
C.
distanceFromWatfordJunction
Indicates the spatial distance between a given location and Watford Junction.
-
D.
distanceToRiverSevern
Indicates the measured distance between a given location or object and the River Severn.
-
E.
distanceFromSouthStation
Indicates the measured distance between a given location or entity and South Station.
- F. None of above. chosen
Provenance (4 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a035b78140081908e451cb63d3c1c7c |
completed | May 12, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_6a035af3d8f48190bf1f3741d374404e |
completed | May 12, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_6a035b773898819099125a5efc239d3e |
completed | May 12, 2026, 4:55 p.m. |
Created at: May 1, 2026, 12:49 a.m.