Triple
T3701418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Darent |
E78586
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Farningham |
E267139
|
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: Farningham | Statement: [River Darent, flowsThrough, Farningham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Farningham Context triple: [River Darent, flowsThrough, Farningham]
-
A.
Farningham
chosen
Farningham is a historic village in the Sevenoaks District of Kent, England, known for its rural character and location on the River Darent.
-
B.
Freckenham
Freckenham is a small rural village and civil parish located in the English county of Suffolk.
-
C.
Folkingham
Folkingham is a historic village in Lincolnshire, England, known for its medieval market heritage and distinctive Georgian architecture.
-
D.
Haddenham
Haddenham is a village and civil parish in Cambridgeshire, England, known for its rural character and historic parish church.
-
E.
Haddenham
Haddenham is a large village in Buckinghamshire, England, known for its historic architecture and rural setting near the town of Thame.
- 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.