Triple
T8010446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burgh Heath |
E186474
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | Tadworth |
E614117
|
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: Tadworth | Statement: [Burgh Heath, hasPostTown, Tadworth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tadworth Context triple: [Burgh Heath, hasPostTown, Tadworth]
-
A.
Tadworth
chosen
Tadworth is a suburban village in Surrey, England, situated on the North Downs and known for its residential character and proximity to Epsom Downs.
-
B.
Harmondsworth
Harmondsworth is a village in the London Borough of Hillingdon, England, known for its historic Great Barn and proximity to Heathrow Airport.
-
C.
Tolworth
Tolworth is a suburban area in the Royal Borough of Kingston upon Thames in southwest London, England.
-
D.
Oxted
Oxted is a commuter town in southeast England known for its proximity to London and location at the foot of the North Downs.
-
E.
Purley
Purley is a suburban town in South London known for its residential character and location within the London Borough of Croydon.
- 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3d70caf8819090a9f98025470c0d |
completed | March 31, 2026, 3:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19f4a2bd881909745f349d847ca87 |
completed | April 4, 2026, 11:31 p.m. |
Created at: March 30, 2026, 5:19 p.m.