Triple
T8979809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Irthing |
E214493
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Gilsland |
E212287
|
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: Gilsland | Statement: [River Irthing, near, Gilsland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gilsland Context triple: [River Irthing, near, Gilsland]
-
A.
Gilsland
chosen
Gilsland is a village in northern England known for its proximity to Hadrian’s Wall and several Roman archaeological sites.
-
B.
Bilsdale
Bilsdale is a rural valley in the North York Moors of North Yorkshire, England, known for its moorland scenery and scattered farming communities.
-
C.
Gisburn
Gisburn is a small rural village and civil parish in Lancashire, England, situated within the Ribble Valley district.
-
D.
Ryhope
Ryhope is a coastal village and suburb of Sunderland in North East England, historically rooted in coal mining and agriculture.
-
E.
Ribblehead
Ribblehead is a remote hamlet in North Yorkshire, England, best known for its dramatic moorland setting and the iconic Ribblehead Viaduct on the Settle–Carlisle railway.
- 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_69ca839ea8b88190922c6a326ffcc0d3 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67a615b081909b88e761be879802 |
completed | April 1, 2026, 12:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc9719f5c8190bc22c3c7375b54f7 |
completed | April 3, 2026, 2:06 p.m. |
Created at: March 30, 2026, 7:03 p.m.