Triple
T1110051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunbridge Wells borough |
E25572
|
entity |
| Predicate | hasParish |
P35
|
FINISHED |
| Object | Pembury |
E126967
|
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: Pembury | Statement: [Tunbridge Wells borough, hasParish, Pembury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pembury Context triple: [Tunbridge Wells borough, hasParish, Pembury]
-
A.
Pembury
chosen
Pembury is a village and civil parish in Kent, England, situated near the town of Royal Tunbridge Wells.
-
B.
Haslemere
Haslemere is a historic market town in the southwest of Surrey, England, near the borders with Hampshire and West Sussex.
-
C.
Hawkenbury
Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
-
D.
Brading
Brading is a small historic town and civil parish on the Isle of Wight in England, known for its Roman villa remains and medieval heritage.
-
E.
Heath End
Heath End is a suburban area and residential locality within the town of Farnham in Surrey, England.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bb75eec08190b1d6545e96816d34 |
completed | March 1, 2026, 10:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac53935d108190955343cd1d3716b0 |
completed | March 7, 2026, 4:34 p.m. |
Created at: March 1, 2026, 7:43 p.m.