Triple
T23373246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bromham Churchyard |
E593531
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Bromham |
—
|
NE NERFINISHED |
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: Bromham | Statement: [Bromham Churchyard, locatedIn, Bromham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bromham Context triple: [Bromham Churchyard, locatedIn, Bromham]
-
A.
Bromham
Bromham is a village in Wiltshire, England, known in part as the place where the Irish poet and songwriter Thomas Moore died.
-
B.
Bromham
chosen
Bromham is a village and civil parish in Bedfordshire, England, known for its historic bridge over the River Great Ouse and its proximity to the town of Bedford.
-
C.
Bloxham
Bloxham is a large historic village in Oxfordshire, England, known for its medieval church and traditional stone-built architecture.
-
D.
Bromyard
Bromyard is a small market town in Herefordshire, England, known for its rural setting and traditional local festivals.
-
E.
Bramfield
Bramfield is a small rural village in Suffolk, England, known for its historic church and traditional English countryside setting.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3b0bc3c8190b1093f7ea29d015c |
completed | April 29, 2026, 6:22 a.m. |
Created at: April 17, 2026, 5:33 p.m.