Triple
T4804379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Rye |
E106911
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Ryedale |
E94725
|
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: Ryedale | Statement: [River Rye, region, Ryedale]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ryedale Context triple: [River Rye, region, Ryedale]
-
A.
Ryedale
chosen
Ryedale is a largely rural district in North Yorkshire, England, known for its market towns, agricultural landscape, and proximity to the North York Moors National Park.
-
B.
Horncastle
Horncastle is a historic market town in Lincolnshire, England, known for its antique shops and its location near the Lincolnshire Wolds.
-
C.
Teesdale
Teesdale is a scenic valley in northern England known for its rugged landscapes, the River Tees, and notable waterfalls such as High Force.
-
D.
Mirfield
Mirfield is a small town in West Yorkshire, England, known for its position on major rail routes and its historic textile industry.
-
E.
Bridlington
Bridlington is a coastal town and popular seaside resort on the North Sea in the East Riding of Yorkshire, 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6c664c3c81908e4d9a7c8c19744b |
completed | March 20, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be67c7f95081908db25bc4c8931671 |
completed | March 21, 2026, 9:41 a.m. |
Created at: March 20, 2026, 1:23 p.m.