Triple
T10175468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thames and Severn Canal |
E235840
|
entity |
| Predicate | terminus |
P388
|
FINISHED |
| Object |
Inglesham
Inglesham is a small village in Wiltshire, England, near the River Thames, known historically as the eastern terminus of the Thames and Severn Canal.
|
E846171
|
NE FINISHED |
How this triple was built (4 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: Inglesham | Statement: [Thames and Severn Canal, terminus, Inglesham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Inglesham Context triple: [Thames and Severn Canal, terminus, Inglesham]
-
A.
Empingham
Empingham is a village in the county of Rutland in the East Midlands of England, known for its proximity to Rutland Water reservoir.
-
B.
Elsenham
Elsenham is a village and civil parish in the Uttlesford district of Essex, England, known for its rural character and railway station on the West Anglia Main Line.
-
C.
Etchingham
Etchingham is a rural village and civil parish in East Sussex, England, known for its historic church and location in the Rother district.
-
D.
Emmington
Emmington is a small settlement in Oxfordshire, England, forming part of the civil parish of Chinnor.
-
E.
Bassingham
Bassingham is a small rural village and civil parish in the North Kesteven district of Lincolnshire, England.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Inglesham Triple: [Thames and Severn Canal, terminus, Inglesham]
Generated description
Inglesham is a small village in Wiltshire, England, near the River Thames, known historically as the eastern terminus of the Thames and Severn Canal.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Inglesham Target entity description: Inglesham is a small village in Wiltshire, England, near the River Thames, known historically as the eastern terminus of the Thames and Severn Canal.
-
A.
Empingham
Empingham is a village in the county of Rutland in the East Midlands of England, known for its proximity to Rutland Water reservoir.
-
B.
Elsenham
Elsenham is a village and civil parish in the Uttlesford district of Essex, England, known for its rural character and railway station on the West Anglia Main Line.
-
C.
Etchingham
Etchingham is a rural village and civil parish in East Sussex, England, known for its historic church and location in the Rother district.
-
D.
Emmington
Emmington is a small settlement in Oxfordshire, England, forming part of the civil parish of Chinnor.
-
E.
Bassingham
Bassingham is a small rural village and civil parish in the North Kesteven district of Lincolnshire, England.
- F. None of above. chosen
Provenance (5 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_69ca84d1d5f88190ab878a1021ecff68 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdecd26a8c8190a391b9d5e47ebb72 |
completed | April 2, 2026, 4:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d3011742b48190bc8b8b6ba03c32b0 |
completed | April 6, 2026, 12:40 a.m. |
| NEDg | Description generation | batch_69d3028994fc81908507449a10e7e093 |
completed | April 6, 2026, 12:47 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d3031ed1e88190b9906338285a6e46 |
completed | April 6, 2026, 12:49 a.m. |
Created at: March 30, 2026, 9:11 p.m.