Triple
T14091012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afon Eden |
E339129
|
entity |
| Predicate | tributaryOf |
P415
|
FINISHED |
| Object | Afon Mawddach |
E899170
|
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: Afon Mawddach | Statement: [Afon Eden, tributaryOf, Afon Mawddach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Afon Mawddach Context triple: [Afon Eden, tributaryOf, Afon Mawddach]
-
A.
Afon Mawddach
chosen
Afon Mawddach is a river in Gwynedd, Wales, known for its scenic estuary near Barmouth and its historical significance to the surrounding valleys and settlements.
-
B.
Afon Dwyfor
Afon Dwyfor is a river in Gwynedd, Wales, that flows through the village of Llanystumdwy before reaching the sea near Criccieth.
-
C.
Afon Taf
Afon Taf is a river in southwest Wales that flows through Carmarthenshire before reaching the sea at Carmarthen Bay.
-
D.
Afon Barlwyd
Afon Barlwyd is a river in Gwynedd, Wales, that flows through the former slate-mining town of Blaenau Ffestiniog and its surrounding mountainous landscape.
-
E.
Afon Ogwen
Afon Ogwen is a river in Snowdonia, north Wales, known for flowing from the Ogwen Valley past Llyn Ogwen towards the sea near Bangor.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5ee3213c8190af2853a2a5b302a2 |
completed | April 14, 2026, 3:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6476c15881909881b9f85697a9b2 |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 9, 2026, 10:21 p.m.