Triple
T14700150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Costessey |
E345273
|
entity |
| Predicate | distanceToNorwichCityCentre |
P4778
|
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: [Costessey, distanceToNorwichCityCentre, approximately 4 miles west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNorwichCityCentre Context triple: [Costessey, distanceToNorwichCityCentre, approximately 4 miles west]
-
A.
distanceFromNorwich
chosen
Indicates the measured distance between a given place or object and the location of Norwich.
-
B.
distanceToYorkCityCentre
Indicates the measured or specified distance between a given location and the centre of York city.
-
C.
directionFromNorwich
Indicates the relative compass direction or bearing of one place or object as measured outward starting from Norwich.
-
D.
distanceFromCambridgeCentre
Indicates the spatial distance between a given entity and the central point of Cambridge.
-
E.
distanceToChesterCityCentre
Indicates the measured or specified distance between a given location and the centre of Chester city.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb605f5948190ab6b20887c4b6833 |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.