Triple
T3543302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botley Hill |
E74936
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Woldingham |
E359887
|
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: Woldingham | Statement: [Botley Hill, locatedNear, Woldingham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Woldingham Context triple: [Botley Hill, locatedNear, Woldingham]
-
A.
Woldingham
chosen
Woldingham is a rural village and civil parish in Surrey, England, known for its affluent residential character and location on the North Downs.
-
B.
Warlingham
Warlingham is a village and civil parish in Surrey, England, situated on the North Downs and functioning largely as a commuter settlement for London.
-
C.
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.
-
D.
Bletchingley
Bletchingley is a historic village in Surrey, England, known for its medieval origins and picturesque rural setting.
-
E.
Beckenham
Beckenham is a suburban town in southeast London known for its residential character, green spaces, and commuter links into central London.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbf752dd481909226044ffe595338 |
completed | March 8, 2026, 6:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b402dfb0688190a65b41c8dc13ee97 |
completed | March 13, 2026, 12:28 p.m. |
Created at: March 8, 2026, 3:20 p.m.