Triple
T7442816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Effingham, Surrey, England |
E171795
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Bookham |
E235905
|
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: Bookham | Statement: [Effingham, Surrey, England, nearbySettlement, Bookham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bookham Context triple: [Effingham, Surrey, England, nearbySettlement, Bookham]
-
A.
Bookham
chosen
Bookham is a village in Surrey, England, known for its residential character and proximity to the North Downs countryside.
-
B.
Hanham
Hanham is a suburban village and residential area on the eastern edge of Bristol in South West England.
-
C.
Brockham
Brockham is a picturesque village in Surrey, England, known for its traditional village green and historic rural character.
-
D.
Mickleham
Mickleham is a small village in Surrey, England, situated in the North Downs between Dorking and Leatherhead.
-
E.
Chobham
Chobham is a village and civil parish in Surrey, England, known for its rural character, common land, and historic buildings.
- 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_69c68a65402881908f7869368eb746fb |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f36d0fbc81908cb7cfe99f80de08 |
completed | March 27, 2026, 9:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8279c9cec8190bde450f845f7d0ea |
completed | March 28, 2026, 7:10 p.m. |
Created at: March 27, 2026, 3:13 p.m.