Triple
T19097890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Donside |
E467454
|
entity |
| Predicate | mainRiver |
P165
|
FINISHED |
| Object | River Don |
—
|
NE NERFINISHED |
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 Don | Statement: [Upper Donside, mainRiver, River Don]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Don Context triple: [Upper Donside, mainRiver, River Don]
-
A.
River Don
The River Don is a major waterway in South Yorkshire, England, historically central to the region’s industrial development and the city of Sheffield.
-
B.
River Don
chosen
The River Don is a major river in northeast Scotland that flows from the Grampian Mountains through Aberdeenshire to the North Sea near Aberdeen.
-
C.
River Tar
The River Tar is a smaller watercourse in Ireland that feeds into the larger River Suir within its catchment area.
-
D.
Ave River
The Ave River is a watercourse in northern Portugal that flows through the Minho region before emptying into the Atlantic Ocean near the city of Vila do Conde.
-
E.
River Dour
The River Dour is a small chalk stream in Kent, England, that flows through the Dover area and historically powered local mills.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e36b279c819091a8d51f044bc644 |
completed | April 20, 2026, 8:27 a.m. |
Created at: April 10, 2026, 12:04 p.m.