Triple
T204416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runnymede |
E4579
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Egham |
E28216
|
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: Egham | Statement: [Runnymede, near, Egham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Egham Context triple: [Runnymede, near, Egham]
-
A.
Egham
chosen
Egham is a town in the county of Surrey in southeast England, known for its proximity to Runnymede, where Magna Carta was sealed.
-
B.
Esher
Esher is a suburban town in the borough of Elmbridge in Surrey, England, known for its affluent residential character and proximity to London.
-
C.
Chertsey
Chertsey is a historic town in southeast England, known for its medieval abbey heritage and location on the River Thames.
-
D.
Sunbury-on-Thames
Sunbury-on-Thames is a suburban town on the River Thames in south-east England, historically part of Middlesex and now within the borough of Spelthorne.
-
E.
Oxted
Oxted is a commuter town in southeast England known for its proximity to London and location at the foot of the North Downs.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25be898ec8190b5e752a1d3b6f466 |
completed | Feb. 28, 2026, 3:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3836ea55c81909135f5f061e47da5 |
completed | March 1, 2026, 12:08 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.