Triple
T19733933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glossop Brook |
E473924
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Gamesley |
E467206
|
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: Gamesley | Statement: [Glossop Brook, flowsThrough, Gamesley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gamesley Context triple: [Glossop Brook, flowsThrough, Gamesley]
-
A.
Gamesley
chosen
Gamesley is a residential area and former council estate on the outskirts of Glossop in Derbyshire, England.
-
B.
Edgeley
Edgeley is a suburban area in Stockport, Greater Manchester, historically part of Cheshire, known for its residential character and proximity to Stockport town centre.
-
C.
Hellingly
Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish church.
-
D.
Godalming
Godalming is a historic market town in southeast England known for its picturesque streets, riverside setting, and role as a commuter hub for London.
-
E.
Tesseney
Tesseney is a town in western Eritrea near the Sudanese border, serving as a local commercial and agricultural center in the Gash-Barka region.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6515b4d308190af3be1787fa7c65b |
completed | April 20, 2026, 4:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07b4f4e1e081908fca0b6513bb3bbb |
completed | May 16, 2026, 12:06 a.m. |
Created at: April 10, 2026, 1:47 p.m.