Triple
T7162985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esher Common |
E166992
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Claygate |
E140611
|
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: Claygate | Statement: [Esher Common, near, Claygate]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Claygate Context triple: [Esher Common, near, Claygate]
-
A.
Claygate
chosen
Claygate is a suburban village in Surrey, England, known for its leafy residential character and commuter links to London.
-
B.
Clappersgate
Clappersgate is a small hamlet in the Lake District of Cumbria, England, situated near Ambleside and known for its scenic riverside setting.
-
C.
Saltergate
Saltergate is a small hamlet in North Yorkshire, England, known as a popular stopping point on the A169 road overlooking the scenic Hole of Horcum in the North York Moors.
-
D.
Bailgate
Bailgate is a historic street in Lincoln, England, known for its Roman heritage, including landmarks such as Newport Arch, and its mix of shops, restaurants, and period architecture.
-
E.
Canongate
Canongate is a historic street and district in Edinburgh’s Old Town, known for its royal connections and significant civic and religious 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e82feee481908fa180ea8c9924fa |
completed | March 27, 2026, 8:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7adc8b06c81909791e38becb594f6 |
completed | March 28, 2026, 10:30 a.m. |
Created at: March 27, 2026, 2:47 p.m.