Triple
T3701417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Darent |
E78586
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Eynsford |
E267140
|
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: Eynsford | Statement: [River Darent, flowsThrough, Eynsford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eynsford Context triple: [River Darent, flowsThrough, Eynsford]
-
A.
Eynsford
chosen
Eynsford is a historic village in the Sevenoaks District of Kent, England, known for its medieval castle ruins and picturesque rural setting.
-
B.
Aylesford
Aylesford is a historic village in Kent, England, known for its ancient bridge, riverside setting, and archaeological significance.
-
C.
Sharneyford
Sharneyford is a small settlement in Lancashire, England, situated within the Rossendale Valley near the border with West Yorkshire.
-
D.
Glanford
Glanford was a former local government district in Lincolnshire, England, that was abolished in the 1990s local government reorganization.
-
E.
Bramford
Bramford is a village and civil parish located near Ipswich in the county of Suffolk, England.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc547c1848190a1ece46c59b7c43d |
completed | March 8, 2026, 6:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4cdf1b16081909b18af630d0b4817 |
completed | March 14, 2026, 2:54 a.m. |
Created at: March 8, 2026, 3:26 p.m.