Triple
T6870777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paddock Wood |
E158537
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Brenchley |
E163458
|
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: Brenchley | Statement: [Paddock Wood, nearbySettlement, Brenchley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brenchley Context triple: [Paddock Wood, nearbySettlement, Brenchley]
-
A.
Brenchley
chosen
Brenchley is a rural village in Kent, England, known for its historic buildings and picturesque countryside setting.
-
B.
Bletchingley
Bletchingley is a historic village in Surrey, England, known for its medieval origins and picturesque rural setting.
-
C.
Frensham
Frensham is a rural village in Surrey, England, known for its scenic commons, ponds, and surrounding countryside.
-
D.
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.
-
E.
Brockham
Brockham is a picturesque village in Surrey, England, known for its traditional village green and historic rural character.
- 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_69c68831e3648190a643c328122e4d43 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8aa47f48190bc7cad3cc652f530 |
completed | March 27, 2026, 7:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c748c0689081908d37d1530ed0f6a0 |
completed | March 28, 2026, 3:19 a.m. |
Created at: March 27, 2026, 2:22 p.m.