Triple
T4676187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Ogmore |
E103686
|
entity |
| Predicate | tributary |
P415
|
FINISHED |
| Object | River Llynfi |
E431606
|
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 Llynfi | Statement: [River Ogmore, tributary, River Llynfi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Llynfi Context triple: [River Ogmore, tributary, River Llynfi]
-
A.
River Llynfi
chosen
River Llynfi is a river in south Wales that flows through the Llynfi Valley and the town of Maesteg before joining the River Ogmore.
-
B.
Afon Glaslyn
Afon Glaslyn is a river in north-west Wales that flows from the mountains of Snowdonia to the sea at Tremadog Bay.
-
C.
Afon Llyfnant
Afon Llyfnant is a small river in mid Wales known for its scenic wooded valley and waterfalls before it joins the River Dyfi.
-
D.
Afon Lliw
Afon Lliw is a river in Wales that flows through the countryside of Gwynedd before reaching Llyn Tegid (Bala Lake).
-
E.
River Vyrnwy
River Vyrnwy is a river in Wales and western England that flows from Lake Vyrnwy through Powys and Shropshire, contributing significantly to the River Severn catchment.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd63685cb88190ac1904e2c7eb6b61 |
completed | March 20, 2026, 3:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be6f8f61b08190ad8913c633369c50 |
completed | March 21, 2026, 10:14 a.m. |
Created at: March 20, 2026, 1:16 p.m.