Triple
T21707200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moreton, Dorset |
E535800
|
entity |
| Predicate | distanceToDorchester |
P145025
|
FINISHED |
| Object | approximately 8 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 8 miles east | Statement: [Moreton, Dorset, distanceToDorchester, approximately 8 miles east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDorchester Context triple: [Moreton, Dorset, distanceToDorchester, approximately 8 miles east]
-
A.
distanceToDorchesterSouth
Indicates the spatial distance between a given entity and the location known as Dorchester South.
-
B.
distanceToShaftesbury
Indicates the measured or calculated distance between a given entity and the location named Shaftesbury.
-
C.
distanceToBasildon
Indicates the spatial distance between a given entity and the location of Basildon.
-
D.
distanceToWinchester
Indicates the spatial distance between a given entity and the location identified as Winchester.
-
E.
distanceToYorkCityCentre
Indicates the measured or specified distance between a given location and the centre of York city.
- F. None of above. chosen
Provenance (4 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb530779c819080204c3bd2f6afa2 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:46 p.m.