Triple
T30973522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gillingham, Dorset |
E789163
|
entity |
| Predicate | distanceToBlandfordForum |
P203440
|
FINISHED |
| Object | approximately 15 miles |
—
|
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 15 miles | Statement: [Gillingham, Dorset, distanceToBlandfordForum, approximately 15 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBlandfordForum Context triple: [Gillingham, Dorset, distanceToBlandfordForum, approximately 15 miles]
-
A.
distanceToBurford
Indicates the spatial distance between a given entity or location and the place named Burford.
-
B.
distanceToBideford_km
Indicates the physical distance, measured in kilometers, between a given place or object and Bideford.
-
C.
distanceToRochford
Indicates the spatial distance between a given entity and the location of Rochford.
-
D.
distanceToBedford
Indicates the measured or specified distance between a given entity or location and Bedford.
-
E.
distanceToBingham
Indicates the measured or calculated distance between a given entity and the location named Bingham.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a017e7bdfe481909cb4d5bdede6035e |
completed | May 11, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_6a017defee108190bdf5f98dc415b250 |
completed | May 11, 2026, 6:57 a.m. |
| PDg | Predicate description generation | batch_6a017e7b0ef4819090f82220b73d0888 |
completed | May 11, 2026, 7 a.m. |
Created at: April 29, 2026, 8:55 p.m.