Triple
T15975707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mickleham |
E387438
|
entity |
| Predicate | hasPostTown |
P2711
|
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: [Mickleham, hasPostTown, Dorking]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dorking Context triple: [Mickleham, hasPostTown, 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.
Purley
Purley is a suburban town in South London known for its residential character and location within the London Borough of Croydon.
-
D.
Chertsey
Chertsey is a small rural settlement in New Zealand’s Canterbury region, situated within the Ashburton District and known for its agricultural surroundings.
-
E.
Chertsey
Chertsey is a historic town in southeast England, known for its medieval abbey heritage and location on the River Thames.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1572c216c81908f2070d2a87609c2 |
completed | April 16, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0025ec39a8819081c0cf996bc59416 |
completed | May 10, 2026, 6:30 a.m. |
Created at: April 10, 2026, 4:54 a.m.