Triple
T9020383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Gipping |
E215707
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Great Blakenham |
E299718
|
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: Great Blakenham | Statement: [River Gipping, flowsThrough, Great Blakenham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Great Blakenham Context triple: [River Gipping, flowsThrough, Great Blakenham]
-
A.
Great Blakenham
chosen
Great Blakenham is a small village and civil parish in Suffolk, England, situated near Ipswich in the East of England.
-
B.
Ranworth Broad
Ranworth Broad is a scenic, wildlife-rich lake in the Norfolk Broads of England, popular for boating, birdwatching, and nature conservation.
-
C.
River Tillingham
The River Tillingham is a small river in East Sussex, England, that flows through the countryside to meet the sea near the historic town of Rye.
-
D.
Great Broughton
Great Broughton is a village in Cumbria, England, known for its rural setting near the Lake District.
-
E.
Wroxham Broad
Wroxham Broad is a popular, scenic boating and wildlife area on the River Bure in the Norfolk Broads of eastern 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a421c2c8190abb12c826066fe75 |
completed | April 1, 2026, 12:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfdbb92ffc81909de907f2bb64dd58 |
completed | April 3, 2026, 3:24 p.m. |
Created at: March 30, 2026, 7:07 p.m.