Triple
T831859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Mole |
E17982
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Esher |
E26463
|
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: Esher | Statement: [River Mole, flowsThrough, Esher]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Esher Context triple: [River Mole, flowsThrough, Esher]
-
A.
Esher
chosen
Esher is a suburban town in the borough of Elmbridge in Surrey, England, known for its affluent residential character and proximity to London.
-
B.
Isleworth
Isleworth is a suburban town in West London, England, known for hosting major media and broadcasting facilities.
-
C.
Egham
Egham is a town in the county of Surrey in southeast England, known for its proximity to Runnymede, where Magna Carta was sealed.
-
D.
Oxted
Oxted is a commuter town in southeast England known for its proximity to London and location at the foot of the North Downs.
-
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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb4be948190ae757df85bdc40e4 |
completed | March 1, 2026, 9:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac8f6056588190af5d66c319ccd0e4 |
completed | March 7, 2026, 8:49 p.m. |
Created at: March 1, 2026, 7:38 p.m.