Triple
T19041381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorchester West |
E466010
|
entity |
| Predicate | distanceToDorchesterSouth |
P133667
|
FINISHED |
| Object | approximately 0.5 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 0.5 miles | Statement: [Dorchester West, distanceToDorchesterSouth, approximately 0.5 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDorchesterSouth Context triple: [Dorchester West, distanceToDorchesterSouth, approximately 0.5 miles]
-
A.
distanceToShaftesbury
Indicates the measured or calculated distance between a given entity and the location named Shaftesbury.
-
B.
distanceToSouthend-on-Sea
Indicates the spatial distance between a given entity and the location Southend-on-Sea.
-
C.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
D.
distanceToBasildon
Indicates the spatial distance between a given entity and the location of Basildon.
-
E.
distanceToYorkCityCentre
Indicates the measured or specified distance between a given location and the centre of York city.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d80118248190af6b4c74df5085ad |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4a3001e388190aa6057266514e75a |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8f6f7c8190af645bf08823ee2b |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:02 p.m.