Triple
T8925172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bardon Mill |
E212521
|
entity |
| Predicate | postTown |
P2711
|
FINISHED |
| Object | HEXHAM |
E212522
|
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: HEXHAM | Statement: [Bardon Mill, postTown, HEXHAM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HEXHAM Context triple: [Bardon Mill, postTown, HEXHAM]
-
A.
Hexham
chosen
Hexham is a historic market town in Northumberland, England, known for its medieval abbey and proximity to Hadrian’s Wall.
-
B.
Hexham Abbey
Hexham Abbey is a historic former Benedictine monastery and parish church in Hexham, Northumberland, renowned for its Anglo-Saxon origins and medieval architecture.
-
C.
Wroxham
Wroxham is a village in Norfolk, England, widely regarded as the main boating and tourist centre of the Norfolk Broads.
-
D.
Fakenham
Fakenham is a market town in Norfolk, England, known historically for its agriculture and as a local commercial center.
-
E.
Uttoxeter
Uttoxeter is a historic market town in central England known for its racecourse and rural Staffordshire setting.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66547de881909ea9bfd104b32893 |
completed | April 1, 2026, 12:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfba58e9ec81909141c516d05ac790 |
completed | April 3, 2026, 1:02 p.m. |
Created at: March 30, 2026, 6:57 p.m.