Triple
T12539088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akenham |
E299788
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Bramford |
E301431
|
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: Bramford | Statement: [Akenham, hasNearbySettlement, Bramford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bramford Context triple: [Akenham, hasNearbySettlement, Bramford]
-
A.
Bramford
chosen
Bramford is a village and civil parish located near Ipswich in the county of Suffolk, England.
-
B.
Brockham
Brockham is a picturesque village in Surrey, England, known for its traditional village green and historic rural character.
-
C.
Bradenham
Bradenham is a village in Norfolk, England, known for its rural setting and proximity to the River Wissey.
-
D.
Bainsford
Bainsford is a district in Falkirk, Scotland, historically associated with local industry and early Scottish football.
-
E.
Barrasford
Barrasford is a small village in Northumberland, England, situated in the Tyne Valley and known for its rural setting and proximity to Hadrian’s Wall.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9546ebf508190ae54857e4289c6e4 |
completed | April 10, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6685f99a08190b6fe4cc10f1c8d73 |
completed | May 2, 2026, 9:10 p.m. |
Created at: April 8, 2026, 9:57 p.m.