Triple
T3508088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fetcham |
E74126
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Ashtead |
E77658
|
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: Ashtead | Statement: [Fetcham, adjacentTo, Ashtead]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashtead Context triple: [Fetcham, adjacentTo, Ashtead]
-
A.
Ashtead
chosen
Ashtead is a large suburban village in Surrey, England, known for its residential character, local amenities, and proximity to the town of Leatherhead.
-
B.
Orsett
Orsett is a village and civil parish in the borough of Thurrock in Essex, England, known for its historic church and traditional village green.
-
C.
Wheathampstead
Wheathampstead is a historic village and civil parish in Hertfordshire, England, known for its rural character and ancient archaeological sites.
-
D.
Twyford
Twyford is a village and civil parish in Berkshire, England, known as a commuter settlement between Reading and London.
-
E.
Northbourne
Northbourne is a small village and civil parish in Kent, England, known for its rural character and historic church.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc0b635c81909bc95ba2562d8f94 |
completed | March 8, 2026, 6:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b44ee6f0488190ab4a1c9065c48753 |
completed | March 13, 2026, 5:52 p.m. |
Created at: March 8, 2026, 3:18 p.m.