Triple
T24055554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sidlesham |
E595792
|
entity |
| Predicate | distanceToChichester |
P154690
|
FINISHED |
| Object | approximately 4 miles south |
—
|
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 south | Statement: [Sidlesham, distanceToChichester, approximately 4 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToChichester Context triple: [Sidlesham, distanceToChichester, approximately 4 miles south]
-
A.
distanceToChesterCityCentre
Indicates the measured or specified distance between a given location and the centre of Chester city.
-
B.
distanceToChesterfield
Indicates the spatial distance between a given entity and the location named Chesterfield.
-
C.
distanceToCirencester
Indicates the spatial distance between a given entity’s location and the town of Cirencester.
-
D.
distanceToColchester
Indicates the spatial distance between a given entity and the location of Colchester.
-
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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9d65e608190b22a81ae4f94daff |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:27 p.m.