Triple
T19127650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rothley Brook |
E468226
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Anstey |
E564995
|
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: Anstey | Statement: [Rothley Brook, flowsThrough, Anstey]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anstey Context triple: [Rothley Brook, flowsThrough, Anstey]
-
A.
Anstey
chosen
Anstey is a large village and civil parish in Leicestershire, England, situated just northwest of Leicester and known historically for its hosiery and footwear industries.
-
B.
Edwardstone
Edwardstone is a small rural village and civil parish in Suffolk, England, known for its historic church and traditional countryside character.
-
C.
Eastry
Eastry is a historic village and civil parish in Kent, England, known for its rural character and proximity to the coastal town of Deal.
-
D.
Ashtead
Ashtead is a large suburban village in Surrey, England, known for its residential character, local amenities, and proximity to the town of Leatherhead.
-
E.
Aylestone
Aylestone is a suburban area of Leicester, England, known for its historic village core and riverside setting along the River Soar.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ceb5808190b3b53d9e8df3605a |
completed | April 20, 2026, 8:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a05e67b296c81909818a4c71380fa98 |
completed | May 14, 2026, 3:12 p.m. |
Created at: April 10, 2026, 12:05 p.m.