Triple
T15114821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sussex |
E361007
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Burgess Hill |
—
|
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: Burgess Hill | Statement: [Sussex, contains, Burgess Hill]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burgess Hill Context triple: [Sussex, contains, Burgess Hill]
-
A.
Burgess Hill
chosen
Burgess Hill is a town in southeastern England known as a commuter hub with residential areas and light industry, situated within the county of West Sussex.
-
B.
Purley
Purley is a suburban town in South London known for its residential character and location within the London Borough of Croydon.
-
C.
Beddington
Beddington is a suburban area in South London known for its historic village core, green spaces, and proximity to Croydon and central London.
-
D.
Redhill
Redhill is a commuter town in southeast England known for its transport links and proximity to London within the county of Surrey.
-
E.
Surbiton
Surbiton is a suburban area in southwest London, England, known for its commuter links to central London and its leafy residential character.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0058f4fb88190a3d446a466aebcf1 |
completed | April 15, 2026, 9:39 p.m. |
Created at: April 10, 2026, 3:05 a.m.