Triple
T19932929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B2139 road |
E479099
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Thakeham |
—
|
NE NERFINISHED |
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: Thakeham | Statement: [B2139 road, passesThrough, Thakeham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thakeham Context triple: [B2139 road, passesThrough, Thakeham]
-
A.
Thakeham
chosen
Thakeham is a rural village and civil parish in West Sussex, England, known for its historic buildings and countryside setting within the Horsham District.
-
B.
Hamtune
Hamtune is an alternative historical spelling of "Hamtun," a place name used in early English records.
-
C.
Weaverham
Weaverham is a large village and civil parish in Cheshire, England, known for its historic buildings and location near the River Weaver.
-
D.
Garboldisham
Garboldisham is a village and civil parish in Norfolk, England, known for its historic country house Garboldisham Hall and rural setting.
-
E.
Thringstone
Thringstone is a village in Leicestershire, England, known for its historic community, former mining connections, and proximity to the town of Coalville.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a14a2348190b41f8e320fe661d6 |
completed | April 20, 2026, 4:53 p.m. |
Created at: April 10, 2026, 1:53 p.m.