Triple
T9773666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Stour |
E237190
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Mersham |
E567441
|
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: Mersham | Statement: [East Stour, flowsThrough, Mersham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mersham Context triple: [East Stour, flowsThrough, Mersham]
-
A.
Mersham
chosen
Mersham is a village in Kent, England, known for its historic rural character and traditional English countryside setting.
-
B.
Westerham
Westerham is a small historic town in Kent, England, known for its picturesque setting and associations with figures such as Winston Churchill.
-
C.
Merstham
Merstham is a village and suburb in Surrey, England, known for its historic centre and proximity to the town of Redhill.
-
D.
Wrotham
Wrotham is a historic village in Kent, England, known for its traditional architecture and rural setting near the North Downs.
-
E.
Faversham
Faversham is a historic market town in Kent, England, known for its medieval architecture, maritime heritage, and long-standing brewing industry.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0f6b8348190bd05b94519de9bc9 |
completed | April 1, 2026, 10:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1c4154af081908ca743b43ade83c7 |
completed | April 5, 2026, 2:08 a.m. |
Created at: March 30, 2026, 8:26 p.m.