Triple
T14820415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bardsea |
E348434
|
entity |
| Predicate | civilParish |
P2739
|
FINISHED |
| Object | Aldingham |
E1111104
|
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: Aldingham | Statement: [Bardsea, civilParish, Aldingham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aldingham Context triple: [Bardsea, civilParish, Aldingham]
-
A.
Aldingham
chosen
Aldingham is a small coastal village and civil parish in Cumbria, England, overlooking Morecambe Bay.
-
B.
Aldbury
Aldbury is a picturesque historic village in Hertfordshire, England, known for its traditional cottages, village pond, and scenic Chilterns countryside setting.
-
C.
Biddenham
Biddenham is a village and civil parish in Bedfordshire, England, situated just west of the town of Bedford.
-
D.
Dersingham
Dersingham is a coastal village in Norfolk, England, known for its proximity to the Royal Sandringham Estate and the nearby Dersingham Bog nature reserve.
-
E.
Bassingham
Bassingham is a small rural village and civil parish in the North Kesteven district of Lincolnshire, 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe4cf38819090f25ef045351d5d |
completed | April 14, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe389bc06c8190a8269c07677d9c35 |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 10, 2026, 1:50 a.m.