Triple
T848432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leith Hill |
E18327
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Dorking |
E26185
|
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: Dorking | Statement: [Leith Hill, near, Dorking]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dorking Context triple: [Leith Hill, near, Dorking]
-
A.
Dorking
chosen
Dorking is a historic market town in southeast England, known for its scenic setting in the Surrey Hills and its traditional high street, vineyards, and surrounding countryside.
-
B.
Oxted
Oxted is a commuter town in southeast England known for its proximity to London and location at the foot of the North Downs.
-
C.
Chertsey
Chertsey is a historic town in southeast England, known for its medieval abbey heritage and location on the River Thames.
-
D.
Esher
Esher is a suburban town in the borough of Elmbridge in Surrey, England, known for its affluent residential character and proximity to London.
-
E.
Farnham
Farnham is a historic market town in southern England known for its Georgian streets, medieval castle, and surrounding Surrey countryside.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac1e41748190a21cd1ce5ebcb8ff |
completed | March 1, 2026, 9:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac939b0fbc8190a205a5033568ba9c |
completed | March 7, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.