Triple
T6372611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kemble |
E143386
|
entity |
| Predicate | distanceToCirencester |
P70250
|
FINISHED |
| Object | approximately 4 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 4 miles | Statement: [Kemble, distanceToCirencester, approximately 4 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToCirencester Context triple: [Kemble, distanceToCirencester, approximately 4 miles]
-
A.
distanceToBicester
Indicates the spatial distance between a given entity and the location of Bicester.
-
B.
distanceToBasingstoke
Indicates the spatial distance between a given entity and the location of Basingstoke.
-
C.
distanceToWhitchurch
Indicates the spatial distance between a given entity and the location named Whitchurch.
-
D.
distanceToChesterCityCentre
Indicates the measured or specified distance between a given location and the centre of Chester city.
-
E.
distanceFromChippenham
Indicates the spatial distance between a given entity or location and Chippenham.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06829d76c819092b476631459233a |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:33 p.m.