Triple
T9769067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bromyard |
E237072
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | BROMYARD |
E237072
|
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: BROMYARD | Statement: [Bromyard, hasPostTown, BROMYARD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BROMYARD Context triple: [Bromyard, hasPostTown, BROMYARD]
-
A.
Bromyard
chosen
Bromyard is a small market town in Herefordshire, England, known for its rural setting and traditional local festivals.
-
B.
Bromham
Bromham is a village in Wiltshire, England, known in part as the place where the Irish poet and songwriter Thomas Moore died.
-
C.
Bramber
Bramber is a historic village in West Sussex, England, known for the ruins of Bramber Castle and its picturesque rural setting.
-
D.
Bawtry
Bawtry is a small historic market town in South Yorkshire, England, known for its traditional high street and role as a local commercial and transport hub.
-
E.
Dyrham
Dyrham is a historic village in South Gloucestershire, England, best known for its picturesque countryside setting and the nearby Dyrham Park estate.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0f0c64c81908f3435dd49c0218b |
completed | April 1, 2026, 10:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1bd05f2588190ab413d26342aa70f |
completed | April 5, 2026, 1:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.