Triple
T6546393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etchingham |
E151018
|
entity |
| Predicate | postalTown |
P2711
|
FINISHED |
| Object | Etchingham |
E151018
|
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: Etchingham | Statement: [Etchingham, postalTown, Etchingham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Etchingham Context triple: [Etchingham, postalTown, Etchingham]
-
A.
Etchingham
chosen
Etchingham is a rural village and civil parish in East Sussex, England, known for its historic church and location in the Rother district.
-
B.
Empingham
Empingham is a village in the county of Rutland in the East Midlands of England, known for its proximity to Rutland Water reservoir.
-
C.
Hensingham
Hensingham is a residential suburb of Whitehaven in Cumbria, England, known for its local community facilities and proximity to the town’s centre.
-
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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6adf00aa48190a86a9ad4795363d9 |
completed | March 27, 2026, 4:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6d54b6d8c819083595375194aee12 |
completed | March 27, 2026, 7:06 p.m. |
Created at: March 27, 2026, 1:50 p.m.