Triple
T22725345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimberley, Nottinghamshire |
E561976
|
entity |
| Predicate | hasDistanceToNottingham |
P26924
|
FINISHED |
| Object | approximately 6 miles northwest |
—
|
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 northwest | Statement: [Kimberley, Nottinghamshire, hasDistanceToNottingham, approximately 6 miles northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistanceToNottingham Context triple: [Kimberley, Nottinghamshire, hasDistanceToNottingham, approximately 6 miles northwest]
-
A.
distanceToNottingham
chosen
Indicates the measured or estimated distance between a given location or entity and the city of Nottingham.
-
B.
distanceToNuneaton
Indicates the spatial distance between a given location or entity and the town of Nuneaton.
-
C.
directionFromNottingham
Indicates the directional relationship of a location or entity as measured outward from Nottingham.
-
D.
distanceToStokeOnTrent
Indicates the measured distance between a given entity’s location and the location of Stoke-on-Trent.
-
E.
distanceToGrantham
Indicates the spatial distance between a given entity and the location of Grantham.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17929710c81909a895622ee32920e |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:20 p.m.