Triple
T16548042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonymaen |
E401995
|
entity |
| Predicate | hasWelshName |
P4705
|
FINISHED |
| Object | Bôn-y-maen |
E401995
|
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: Bôn-y-maen | Statement: [Bonymaen, hasWelshName, Bôn-y-maen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bôn-y-maen Context triple: [Bonymaen, hasWelshName, Bôn-y-maen]
-
A.
Bonymaen
chosen
Bonymaen is a residential district and community in the east of Swansea, Wales.
-
B.
Brynaman
Brynaman is a village in Carmarthenshire, Wales, situated on the edge of the Black Mountain in the Brecon Beacons and known historically for its coal mining heritage.
-
C.
Y Bermo
Y Bermo is the Welsh name for the coastal town of Barmouth in Gwynedd, northwest Wales.
-
D.
Breydin
Breydin is a small municipality in the district of Barnim in the federal state of Brandenburg in northeastern Germany.
-
E.
Binghame
Binghame is an alternative spelling or variant form of the name Bingham, which is used as a surname and place name.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fbf79048190b761008441762374 |
completed | April 18, 2026, 9:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006edbd8388190b9a96c1cc5c9119e |
completed | May 10, 2026, 11:41 a.m. |
Created at: April 10, 2026, 5:15 a.m.