Triple
T24409030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Barrington, Gloucestershire, England |
E615392
|
entity |
| Predicate | distanceToCheltenham |
P155823
|
FINISHED |
| Object | approximately 20 miles east-southeast |
—
|
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 20 miles east-southeast | Statement: [Great Barrington, Gloucestershire, England, distanceToCheltenham, approximately 20 miles east-southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToCheltenham Context triple: [Great Barrington, Gloucestershire, England, distanceToCheltenham, approximately 20 miles east-southeast]
-
A.
distanceToChesterfield
Indicates the spatial distance between a given entity and the location named Chesterfield.
-
B.
distanceToChichester
Indicates the measured distance between a given location or entity and the place Chichester.
-
C.
distanceFromChippenham
Indicates the spatial distance between a given entity or location and Chippenham.
-
D.
distanceToChepstow
Indicates the spatial distance between a given entity and the location of Chepstow.
-
E.
distanceToThatcham
Indicates the measured or specified distance from a given entity or location to Thatcham.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2957fab0481909121c6da6b5e34c0 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f2915233c48190a181c8c1924e892c |
completed | April 29, 2026, 11:16 p.m. |
Created at: April 18, 2026, 2:05 a.m.