Triple
T8971441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BH postcode area |
E214274
|
entity |
| Predicate | coversTown |
P847
|
FINISHED |
| Object | Blandford Forum |
E42251
|
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: Blandford Forum | Statement: [BH postcode area, coversTown, Blandford Forum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Blandford Forum Context triple: [BH postcode area, coversTown, Blandford Forum]
-
A.
Blandford Forum
chosen
Blandford Forum is a historic market town on the River Stour in Dorset, England, noted for its Georgian architecture and rural surroundings.
-
B.
Blyford
Blyford is a small rural village located in the English county of Suffolk.
-
C.
Grindon
Grindon is a residential suburb of Sunderland in the Wearside area of North East England.
-
D.
Southwold
Southwold is a small seaside town and popular tourist resort on the North Sea coast of Suffolk, England, known for its pier, beach huts, and historic lighthouse.
-
E.
Southwold
Southwold is a residential neighbourhood within the town of Bicester in Oxfordshire, England.
- 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6780d45081909f2bc5295c8550f9 |
completed | April 1, 2026, 12:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc9632afc8190a4dc14d33e8757ee |
completed | April 3, 2026, 2:06 p.m. |
Created at: March 30, 2026, 7:02 p.m.