Triple
T9869196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Misbourne |
E239911
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Old Amersham |
E229376
|
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: Old Amersham | Statement: [River Misbourne, flowsThrough, Old Amersham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Old Amersham Context triple: [River Misbourne, flowsThrough, Old Amersham]
-
A.
Aldermaston Court
Aldermaston Court is a historic country house and estate in Aldermaston, Berkshire, known for its architectural and heritage significance.
-
B.
Amersham
chosen
Amersham is a historic market town in southeast England known for its picturesque old town, Chilterns countryside setting, and role as a commuter hub into London.
-
C.
Foxhall
Foxhall is a small rural village and civil parish located in the county of Suffolk in eastern England.
-
D.
Goodnestone
Goodnestone is a small rural village and civil parish in Kent, England, known for its historic church and the nearby Goodnestone Park estate.
-
E.
Rushmere
Rushmere is a village and civil parish located in the English county of Suffolk.
- 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_69ca84e7506c819095cbde4ff16512bb |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3d498b481908f82f31f98b57c7e |
completed | April 2, 2026, 12:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1e46209988190b97aefee6cbddbad |
completed | April 5, 2026, 4:26 a.m. |
Created at: March 30, 2026, 8:36 p.m.