Triple
T32405509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forsbrook |
E828065
|
entity |
| Predicate | distanceFromStokeOnTrent |
P68053
|
FINISHED |
| Object | approximately 7 miles south-east |
—
|
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 7 miles south-east | Statement: [Forsbrook, distanceFromStokeOnTrent, approximately 7 miles south-east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromStokeOnTrent Context triple: [Forsbrook, distanceFromStokeOnTrent, approximately 7 miles south-east]
-
A.
distanceToStokeOnTrent
chosen
Indicates the measured distance between a given entity’s location and the location of Stoke-on-Trent.
-
B.
distanceToBurtonUponTrent
Indicates the measured distance between a given entity and the location of Burton upon Trent.
-
C.
distanceToCrewe
Indicates the spatial distance between an entity and the location Crewe.
-
D.
distanceToNottingham
Indicates the measured or estimated distance between a given location or entity and the city of Nottingham.
-
E.
distanceToManchester
Indicates the measured or calculated distance between a given entity’s location and the city of Manchester.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a036fb4650c81908df9b9ec8ed8594b |
completed | May 12, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_6a036f64dc648190a31cf944d3ea0f7d |
completed | May 12, 2026, 6:20 p.m. |
Created at: May 1, 2026, 12:53 a.m.