Triple
T3270637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Tamar |
E68638
|
entity |
| Predicate | tributary |
P415
|
FINISHED |
| Object | River Lynher |
E350305
|
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 Lynher | Statement: [River Tamar, tributary, River Lynher]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Lynher Context triple: [River Tamar, tributary, River Lynher]
-
A.
River Lynher
chosen
The River Lynher is a river in southeast Cornwall, England, that flows through rural valleys and tidal creeks before joining the Tamar estuary near Plymouth.
-
B.
River Kenwyn
River Kenwyn is a small river in Truro, Cornwall, that flows through the city and contributes to its historic harbour and local landscape.
-
C.
Lez River
The Lez River is a short coastal river in southern France that flows through the city of Montpellier before emptying into the Mediterranean Sea.
-
D.
River Tavy
River Tavy is a river in Devon, England, that flows through the town of Tavistock before joining the River Tamar.
-
E.
River Ivel
The River Ivel is a river in Bedfordshire, England, that flows northward through towns such as Biggleswade and Sandy before joining the River Great Ouse.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adaff349148190beae8c0994b7ad83 |
completed | March 8, 2026, 5:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b37e49fa3c8190baa956a311b1a716 |
completed | March 13, 2026, 3:02 a.m. |
Created at: March 8, 2026, 3:09 p.m.