Triple
T18853739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deganwy |
E461115
|
entity |
| Predicate | hasNeighbouringSettlement |
P4647
|
FINISHED |
| Object | Conwy |
—
|
NE NERFINISHED |
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: Conwy | Statement: [Deganwy, hasNeighbouringSettlement, Conwy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Conwy Context triple: [Deganwy, hasNeighbouringSettlement, Conwy]
-
A.
Conwy
chosen
Conwy is a county borough in north Wales known for its historic walled town, medieval castle, and scenic coastal and mountainous landscapes.
-
B.
Aberconwy
Aberconwy is a UK parliamentary constituency in North Wales that includes parts of Conwy County Borough and surrounding areas.
-
C.
Ffestiniog
Ffestiniog is a historic town in north Wales, known for its slate quarrying heritage and proximity to the scenic landscapes of Snowdonia.
-
D.
Deganwy
Deganwy is a coastal village in Conwy County Borough, Wales, situated on the Conwy estuary opposite Conwy and near the resort town of Llandudno.
-
E.
Tynewydd
Tynewydd is a small village in the Rhondda Valley of South Wales, historically associated with coal mining communities near Treherbert.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c05b4d8881909af0238f451b0e31 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 10, 2026, 11:56 a.m.