Triple
T14676028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Higher Hodder Bridge |
E344648
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Hurst Green |
E244050
|
NE 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: Hurst Green | Statement: [Higher Hodder Bridge, near, Hurst Green]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hurst Green Context triple: [Higher Hodder Bridge, near, Hurst Green]
-
A.
Hurst Green
chosen
Hurst Green is a small village in Lancashire, England, known for its scenic countryside near the River Ribble and its association with Stonyhurst College.
-
B.
Hurst Green
Hurst Green is a village and residential area in Surrey, England, situated within the Tandridge District and typically regarded as part of the Oxted area.
-
C.
Rushey Green
Rushey Green is a district and major thoroughfare in the London Borough of Lewisham, forming part of the wider Lewisham East area.
-
D.
Weston Green
Weston Green is a small suburban area in Surrey, England, situated close to the village of Thames Ditton and within the commuter belt of Greater London.
-
E.
Wooburn Green
Wooburn Green is a village and large green in Buckinghamshire, England, situated near High Wycombe in the River Wye valley.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb5666e648190b5faa07076f497b8 |
completed | April 14, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe24a6b0908190943f193f5a17ec8c |
completed | May 8, 2026, 6 p.m. |
Created at: April 10, 2026, 1:27 a.m.