Triple
T14471570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burghfield |
E358854
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Burghfield Village |
E358854
|
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: Burghfield Village | Statement: [Burghfield, hasSettlement, Burghfield Village]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burghfield Village Context triple: [Burghfield, hasSettlement, Burghfield Village]
-
A.
Burghfield
chosen
Burghfield is a village and civil parish in Berkshire, England, known for its rural character and proximity to Reading.
-
B.
Burgh Heath
Burgh Heath is a residential area and local community within the borough of Reigate and Banstead in Surrey, England.
-
C.
Burghfield Common
Burghfield Common is a large residential village in West Berkshire, England, known for its commuter links to Reading and surrounding towns.
-
D.
Bedworth Heath
Bedworth Heath is a residential area and suburb situated on the outskirts of the town of Bedworth in Warwickshire, England.
-
E.
Oldbury
Oldbury is a town in the West Midlands of England that serves as the administrative centre of the Metropolitan Borough of Sandwell.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91f969788190a5114f92d7159aae |
completed | April 14, 2026, 7:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6d8ae5508190aea1cab0b059f804 |
completed | May 8, 2026, 4:58 a.m. |
Created at: April 10, 2026, 1:20 a.m.