Triple
T28863574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Bank |
E728929
|
entity |
| Predicate | distanceFromMiddlesbroughTownCentre |
P86998
|
FINISHED |
| Object | approximately 3 miles 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 3 miles east | Statement: [South Bank, distanceFromMiddlesbroughTownCentre, approximately 3 miles east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromMiddlesbroughTownCentre Context triple: [South Bank, distanceFromMiddlesbroughTownCentre, approximately 3 miles east]
-
A.
distanceFromMiddlesbrough
chosen
Indicates the spatial distance between an entity’s location and the town of Middlesbrough.
-
B.
distanceToBradfordCityCentre
Indicates the spatial distance between a given location and the centre of Bradford city.
-
C.
distanceToOldhamTownCentre
Indicates the measured distance between a given location and the centre of Oldham town.
-
D.
distanceFromLeeds
Indicates the spatial distance between a given entity and the location of Leeds.
-
E.
distanceFromBolton
Indicates the spatial distance between a given entity or location and the place named Bolton.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a004b6ad4248190b402a0d01b0ebf83 |
completed | May 10, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a004ae736b881908a0efed8f63f982e |
completed | May 10, 2026, 9:07 a.m. |
Created at: April 28, 2026, 6:48 a.m.