Triple
T23117253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langley Mill railway station |
E576789
|
entity |
| Predicate | distanceFromNottingham |
P26924
|
FINISHED |
| Object | approximately 10 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 10 miles | Statement: [Langley Mill railway station, distanceFromNottingham, approximately 10 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromNottingham Context triple: [Langley Mill railway station, distanceFromNottingham, approximately 10 miles]
-
A.
distanceToNottingham
chosen
Indicates the measured or estimated distance between a given location or entity and the city of Nottingham.
-
B.
directionFromNottingham
Indicates the directional relationship of a location or entity as measured outward from Nottingham.
-
C.
distanceToStokeOnTrent
Indicates the measured distance between a given entity’s location and the location of Stoke-on-Trent.
-
D.
distanceFromTamworth
Indicates the spatial distance measured from the reference location Tamworth to another place or entity.
-
E.
distanceToBurtonUponTrent
Indicates the measured distance between a given entity and the location of Burton upon Trent.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e4d095081908bad99fab6eaadd0 |
completed | April 29, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:59 p.m.