Triple
T9348588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teversham |
E224956
|
entity |
| Predicate | civilParish |
P2739
|
FINISHED |
| Object | Teversham |
E224956
|
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: Teversham | Statement: [Teversham, civilParish, Teversham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Teversham Context triple: [Teversham, civilParish, Teversham]
-
A.
Teversham
chosen
Teversham is a small village and civil parish located near Cambridge in the South Cambridgeshire district of England.
-
B.
Orsett
Orsett is a village and civil parish in the borough of Thurrock in Essex, England, known for its historic church and traditional village green.
-
C.
Cheshunt
Cheshunt is a town in Hertfordshire, England, situated just north of London and known as a commuter hub with rail links into the capital.
-
D.
Thelnetham
Thelnetham is a small rural village and civil parish in the English county of Suffolk, known for its traditional countryside character and historic buildings.
-
E.
Hamstead
Hamstead is a suburban residential area in the West Midlands, England, situated between Birmingham and 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_69ca842993248190a79ab06968994b86 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4f107f0081908938f4b814eca5fc |
completed | April 1, 2026, 5 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0e432106c81908ae080f37bc80f3f |
completed | April 4, 2026, 10:13 a.m. |
Created at: March 30, 2026, 7:41 p.m.