Triple
T10865848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amble |
E256526
|
entity |
| Predicate | nearby |
P350
|
FINISHED |
| Object | River Coquet |
E181866
|
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 Coquet | Statement: [Amble, nearby, River Coquet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Coquet Context triple: [Amble, nearby, River Coquet]
-
A.
River Coquet
chosen
River Coquet is a river in Northumberland, England, known for its scenic valleys, wildlife, and historic towns along its course.
-
B.
River Aln
The River Aln is a small river in Northumberland, England, that flows through rural landscapes before reaching the North Sea at the coastal village of Alnmouth.
-
C.
Colne River
The Colne River is a tributary of the River Thames in southern England that has historically marked parts of the boundary of Middlesex and neighboring counties.
-
D.
River Ryburn
River Ryburn is a river in West Yorkshire, England, that flows through the Ryburn Valley and joins the River Calder near the town of Sowerby Bridge.
-
E.
River Deerness
River Deerness is a small river in County Durham, England, that flows through the Deerness Valley before joining the River Wear.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7516cebe881909ed358a7641f6a12 |
completed | April 9, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dff7d7b32081909dd5f8ae3fe293be |
completed | April 15, 2026, 8:40 p.m. |
Created at: April 8, 2026, 9:20 p.m.