Triple
T16970952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harnham Conservation Area |
E411676
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Harnham |
E411663
|
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: Harnham | Statement: [Harnham Conservation Area, locatedIn, Harnham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Harnham Context triple: [Harnham Conservation Area, locatedIn, Harnham]
-
A.
Harnham
chosen
Harnham is a suburb of Salisbury in Wiltshire, England, known for its historic buildings and scenic riverside setting near Salisbury Cathedral.
-
B.
Haddenham
Haddenham is a large village in Buckinghamshire, England, known for its historic architecture and rural setting near the town of Thame.
-
C.
Haddenham
Haddenham is a village and civil parish in Cambridgeshire, England, known for its rural character and historic parish church.
-
D.
Hanham
Hanham is a suburban village and residential area on the eastern edge of Bristol in South West England.
-
E.
Harmston
Harmston is a small village and civil parish in Lincolnshire, England, known for its rural character and proximity to the city of Lincoln.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0ac23a48190992fa125fceb1eb2 |
completed | April 18, 2026, 6:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012eccd1e48190aa0dc64562d6ff1f |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:31 a.m.