Triple
T22734840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Ayton |
E562236
|
entity |
| Predicate | distanceToMiddlesbrough |
P86998
|
FINISHED |
| Object | approximately 7 miles south |
—
|
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 | Statement: [Great Ayton, distanceToMiddlesbrough, approximately 7 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMiddlesbrough Context triple: [Great Ayton, distanceToMiddlesbrough, approximately 7 miles south]
-
A.
distanceFromMiddlesbrough
chosen
Indicates the spatial distance between an entity’s location and the town of Middlesbrough.
-
B.
distanceToScunthorpe
Indicates the measured or calculated distance between a given entity’s location and the town of Scunthorpe.
-
C.
distanceToBurnley
Indicates the measured spatial distance between a given entity and the location Burnley.
-
D.
distanceToHuddersfield
Indicates the spatial distance between a given entity or location and the town of Huddersfield.
-
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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1796f030881908e141564d442bd1b |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:22 p.m.