Triple
T13458016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corsham, Wiltshire |
E311282
|
entity |
| Predicate | distanceToChippenham |
P52051
|
FINISHED |
| Object | approximately 4 miles west |
—
|
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 4 miles west | Statement: [Corsham, Wiltshire, distanceToChippenham, approximately 4 miles west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToChippenham Context triple: [Corsham, Wiltshire, distanceToChippenham, approximately 4 miles west]
-
A.
distanceFromChippenham
chosen
Indicates the spatial distance between a given entity or location and Chippenham.
-
B.
distanceToWymondham
Indicates the spatial distance between a given entity or location and Wymondham.
-
C.
distanceToThatcham
Indicates the measured or specified distance from a given entity or location to Thatcham.
-
D.
distanceToFakenham
Indicates the spatial distance between a given entity and the location Fakenham.
-
E.
distanceToHungerford
Indicates the spatial distance between a given entity and the location named Hungerford.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0a75008190a508060c85f73604 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.