Triple
T15114810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sussex |
E361007
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Haywards Heath |
E182110
|
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: Haywards Heath | Statement: [Sussex, contains, Haywards Heath]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Haywards Heath Context triple: [Sussex, contains, Haywards Heath]
-
A.
Haywards Heath
chosen
Haywards Heath is a commuter town in southeastern England known for its strategic railway links between London, Brighton, and the south coast.
-
B.
Burgh Heath
Burgh Heath is a residential area and local community within the borough of Reigate and Banstead in Surrey, England.
-
C.
Surrey Heath
Surrey Heath is a local government district and borough in Surrey, England, encompassing towns and villages such as Bagshot, Camberley, and Frimley.
-
D.
Hertford Heath
Hertford Heath is a village and civil parish in Hertfordshire, England, known for its rural character, common land, and proximity to the town of Hertford.
-
E.
Speldhurst
Speldhurst is a rural village and civil parish in Kent, England, known for its historic church, traditional pubs, and scenic countryside near Royal Tunbridge Wells.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0058f4fb88190a3d446a466aebcf1 |
completed | April 15, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d445c4848190b5c97bb27be6c749 |
completed | May 10, 2026, 6:53 p.m. |
Created at: April 10, 2026, 3:05 a.m.