Triple
T5751025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Llanrhidian |
E126850
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Llangennith |
E119195
|
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: Llangennith | Statement: [Llanrhidian, hasNearbySettlement, Llangennith]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Llangennith Context triple: [Llanrhidian, hasNearbySettlement, Llangennith]
-
A.
Llangennith
chosen
Llangennith is a coastal village in southwest Wales known for its expansive sandy beach and popular surfing conditions.
-
B.
Llangennech
Llangennech is a village in Carmarthenshire, Wales, situated near the Loughor estuary and known for its historic links to coal mining and the Llanelli area.
-
C.
Llanfyllin
Llanfyllin is a small historic market town in Powys, Wales, known for its rural setting near the Berwyn Mountains and its traditional Welsh character.
-
D.
Llanymynech
Llanymynech is a village on the England–Wales border known for its historic limestone quarrying and canal heritage.
-
E.
Llanwddyn
Llanwddyn is a small village in Powys, Wales, best known for its relocation during the late 19th century to make way for the creation of Lake Vyrnwy reservoir.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0288a0ea8819091ac6f965471ceee |
completed | March 22, 2026, 5:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c750f84be081908fa4738e09cb884e |
completed | March 28, 2026, 3:54 a.m. |
Created at: March 22, 2026, 3:48 p.m.