Triple
T12622873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claydon |
E301430
|
entity |
| Predicate | parishIncludes |
P38128
|
FINISHED |
| Object | Barham (part) |
E299717
|
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: Barham (part) | Statement: [Claydon, parishIncludes, Barham (part)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Barham (part) Context triple: [Claydon, parishIncludes, Barham (part)]
-
A.
Barham
chosen
Barham is a village and civil parish located in the county of Suffolk in eastern England.
-
B.
Barham
Barham is a small rural town in the Riverina region of New South Wales, Australia, situated on the Murray River opposite the Victorian town of Koondrook.
-
C.
Partington
Partington is a suburban town and civil parish in the Metropolitan Borough of Trafford, Greater Manchester, England.
-
D.
Boreham
Boreham is a village in Essex, England, known for its rural character and proximity to the town of Chelmsford.
-
E.
Brockham
Brockham is a picturesque village in Surrey, England, known for its traditional village green and historic rural character.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d960c8671881909a102d28b0e7f603 |
completed | April 10, 2026, 8:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65ed6f79881908872c644a9789f04 |
completed | May 2, 2026, 8:30 p.m. |
Created at: April 9, 2026, 5:14 p.m.