Triple
T1298825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montrose |
E27714
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | River South Esk |
E23784
|
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 South Esk | Statement: [Montrose, hasRiver, River South Esk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River South Esk Context triple: [Montrose, hasRiver, River South Esk]
-
A.
River South Esk
chosen
River South Esk is a Scottish river flowing through the county of Angus from the Grampian Mountains to the North Sea at Montrose.
-
B.
River Esk
The River Esk is a scenic river in North Yorkshire, England, flowing through the North York Moors to the North Sea at Whitby.
-
C.
River Esk
The River Esk is a Scottish river that flows through Midlothian and East Lothian, passing towns such as Musselburgh before reaching the North Sea via the Firth of Forth.
-
D.
North Esk River
The North Esk River is a Scottish waterway whose name was adopted as the title for the Earl of Northesk in the Peerage of Scotland.
-
E.
River Brent
The River Brent is a tributary of the River Thames in West London, flowing through several London boroughs and giving its name to the London Borough of Brent.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c111a76c81909e6b914694986251 |
completed | March 1, 2026, 10:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acc622dac88190b6ecdc62c7f26dc5 |
completed | March 8, 2026, 12:43 a.m. |
Created at: March 1, 2026, 7:51 p.m.