Triple
T7293314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Tillingbourne |
E164452
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Chilworth |
E356838
|
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: Chilworth | Statement: [River Tillingbourne, flowsThrough, Chilworth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chilworth Context triple: [River Tillingbourne, flowsThrough, Chilworth]
-
A.
Chieveley
Chieveley is a rural village and civil parish in Berkshire, England, known for its historic church, countryside setting, and proximity to Newbury and major transport routes.
-
B.
Bletchingley
chosen
Bletchingley is a historic village in Surrey, England, known for its medieval origins and picturesque rural setting.
-
C.
Codicote
Codicote is a village and civil parish in the county of Hertfordshire in southern England.
-
D.
Earlswood
Earlswood is a residential suburb and locality in Surrey, England, situated just south of the town of Redhill.
-
E.
Chelsworth
Chelsworth is a small rural village and civil parish in Suffolk, England, known for its historic buildings and picturesque countryside setting.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7e53faa0481909758a7366cbbe99f |
completed | March 28, 2026, 2:27 p.m. |
Created at: March 27, 2026, 3 p.m.