Triple
T2094338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leatherhead |
E32744
|
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: [Leatherhead, near, Dorking]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dorking Context triple: [Leatherhead, 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.
Burgess Hill
Burgess Hill is a town in southeastern England known as a commuter hub with residential areas and light industry, situated within the county of West Sussex.
-
E.
Esher
Esher is a suburban town in the borough of Elmbridge in Surrey, England, known for its affluent residential character and proximity to 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba98c32081908a243bc7088a1510 |
completed | March 7, 2026, 5:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b333ef7f30819086b538cdc2cefe0f |
completed | March 12, 2026, 9:45 p.m. |
Created at: March 4, 2026, 7:43 p.m.