Triple
T12510292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Chelmer |
E299057
|
entity |
| Predicate | flowsNear |
P350
|
FINISHED |
| Object | Boreham |
E609212
|
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: Boreham | Statement: [River Chelmer, flowsNear, Boreham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Boreham Context triple: [River Chelmer, flowsNear, Boreham]
-
A.
Boreham
chosen
Boreham is a village in Essex, England, known for its rural character and proximity to the town of Chelmsford.
-
B.
Brockham
Brockham is a picturesque village in Surrey, England, known for its traditional village green and historic rural character.
-
C.
Barrowfield
Barrowfield is a residential district in Glasgow, Scotland, known historically for its working-class community and proximity to major football and industrial sites in the city's East End.
-
D.
Bramford
Bramford is a village and civil parish located near Ipswich in the county of Suffolk, England.
-
E.
Bromeswell
Bromeswell is a small rural village and civil parish 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9541c1ca08190a4026c394ebcbeb5 |
completed | April 10, 2026, 7:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f64bb94d608190aae4c8ec39556362 |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 8, 2026, 9:57 p.m.