Triple
T11287035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Beult |
E267219
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Staplehurst |
E545708
|
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: Staplehurst | Statement: [River Beult, flowsThrough, Staplehurst]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Staplehurst Context triple: [River Beult, flowsThrough, Staplehurst]
-
A.
Staplehurst
chosen
Staplehurst is a village in Kent, England, known as a rural commuter settlement on the railway line between London and the southeast coast.
-
B.
Wadhurst
Wadhurst is a rural village in East Sussex, England, known for its historic High Street, surrounding Wealden countryside, and role as a commuter community for nearby towns and London.
-
C.
Hawkenbury
Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
-
D.
Goudhurst
Goudhurst is a historic rural village in Kent, England, known for its scenic Wealden countryside, traditional architecture, and prominent hilltop church.
-
E.
Stalham
Stalham is a small market town in Norfolk, England, known as a gateway to the Norfolk Broads.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e986b0f08190a414749eaa7f1a5d |
completed | April 9, 2026, 6:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4f48e190c8190b46d4286e2acaef1 |
completed | April 19, 2026, 3:28 p.m. |
Created at: April 8, 2026, 9:32 p.m.