Triple
T13690953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battisford Parish Council |
E328257
|
entity |
| Predicate | jurisdiction |
P82
|
FINISHED |
| Object | Battisford |
E328257
|
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: Battisford | Statement: [Battisford Parish Council, jurisdiction, Battisford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Battisford Context triple: [Battisford Parish Council, jurisdiction, Battisford]
-
A.
Battisford
chosen
Battisford is a small rural village and civil parish located in the English county of Suffolk.
-
B.
Blyford
Blyford is a small rural village located in the English county of Suffolk.
-
C.
Blatchford
Blatchford is a sustainable, mixed-use residential community being developed on the former Edmonton City Centre Airport lands in Edmonton, Alberta.
-
D.
Belchford
Belchford is a small rural village in eastern England, situated within the scenic, rolling countryside of the Lincolnshire Wolds.
-
E.
Bainsford
Bainsford is a district in Falkirk, Scotland, historically associated with local industry and early Scottish football.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc8746458819095ec1ba3c01ef31b |
completed | April 12, 2026, 4:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b063661481908da569084c20f37c |
completed | May 3, 2026, 8:30 p.m. |
Created at: April 9, 2026, 9:53 p.m.