Triple
T10819292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burgess Hill |
E255320
|
entity |
| Predicate | hasNeighbourhood |
P4813
|
FINISHED |
| Object | Chanctonbury |
E269828
|
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: Chanctonbury | Statement: [Burgess Hill, hasNeighbourhood, Chanctonbury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chanctonbury Context triple: [Burgess Hill, hasNeighbourhood, Chanctonbury]
-
A.
Ringstead
Ringstead is a small rural village in Norfolk, England, situated near the North Sea coast and surrounded by agricultural countryside.
-
B.
Heytesbury
Heytesbury is a historic village and former parliamentary borough in Wiltshire, England.
-
C.
Hawkenbury
Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
-
D.
Chanctonbury Ring
chosen
Chanctonbury Ring is a prehistoric hill fort and distinctive clump of trees on the South Downs in West Sussex, England, known for its archaeological significance, panoramic views, and associated folklore.
-
E.
Holmbury Hill
Holmbury Hill is a prominent wooded hill and Iron Age hillfort site in Surrey, England, known for its extensive views over the surrounding countryside.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734492be88190874ea0ba4d0fa643 |
completed | April 9, 2026, 5:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de8569178481909474e939a3e4c217 |
completed | April 14, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:18 p.m.