Triple
T12383276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawes |
E295794
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | River Ure |
E128035
|
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: River Ure | Statement: [Hawes, hasRiver, River Ure]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Ure Context triple: [Hawes, hasRiver, River Ure]
-
A.
River Ure
chosen
The River Ure is a significant river in North Yorkshire, England, flowing through Wensleydale and forming part of the River Ouse system.
-
B.
River Urr
River Urr is a river in southwest Scotland that flows through Dumfries and Galloway before entering the Solway Firth.
-
C.
River Mein
River Mein is a small river in Dumfries and Galloway in southwest Scotland, flowing near the village of Ecclefechan.
-
D.
Túr River
The Túr River is a watercourse in Eastern Europe that flows through parts of Romania and Hungary before joining the Tisa River.
-
E.
River Brun
River Brun is a small river in Lancashire, England, that flows through the town of Burnley and contributes to its local landscape and waterways.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fbc3f608190b0ee3c4f304a94db |
completed | April 10, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f64b926c5c81909427eb191ae75ec6 |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 8, 2026, 9:54 p.m.