Triple
T32122001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadoxhurst |
E820400
|
entity |
| Predicate | distanceFromAshfordTownCentre |
P60159
|
FINISHED |
| Object | approximately 5 miles south-west |
—
|
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 south-west | Statement: [Shadoxhurst, distanceFromAshfordTownCentre, approximately 5 miles south-west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromAshfordTownCentre Context triple: [Shadoxhurst, distanceFromAshfordTownCentre, approximately 5 miles south-west]
-
A.
distanceToAshford
chosen
Indicates the spatial distance between a given entity and the location named Ashford.
-
B.
distanceToBradfordCityCentre
Indicates the spatial distance between a given location and the centre of Bradford city.
-
C.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
D.
distanceFromBathCityCentre_km
Indicates the distance, measured in kilometers, between an entity and the center of Bath city.
-
E.
approximateDistanceFromTownCentre
Indicates the estimated spatial distance between a given location and the center of a 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a032616547c8190bc877202e43403eb |
completed | May 12, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_6a0325246abc819088e16a7fbadf40c5 |
completed | May 12, 2026, 1:03 p.m. |
Created at: May 1, 2026, 12:28 a.m.