Triple
T5994914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chepstow Racecourse |
E133442
|
entity |
| Predicate | distanceFromBristol |
P42445
|
FINISHED |
| Object | approximately 16 miles northwest |
—
|
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 16 miles northwest | Statement: [Chepstow Racecourse, distanceFromBristol, approximately 16 miles northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBristol Context triple: [Chepstow Racecourse, distanceFromBristol, approximately 16 miles northwest]
-
A.
distanceToBristol
chosen
Indicates the measured or calculated spatial distance between a given entity and the location of Bristol.
-
B.
directionFromBristol
Indicates the cardinal or relative compass direction of one place or object as measured outward starting from Bristol.
-
C.
distanceToBirmingham
Indicates the spatial distance between a given entity’s location and the city of Birmingham.
-
D.
distanceToBrighton
Indicates the measured or specified distance between a given entity or location and Brighton.
-
E.
distanceToBasingstoke
Indicates the spatial distance between a given entity and the location of Basingstoke.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e943dcc8190a09817e8ef0e4188 |
completed | March 22, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.