Triple

T11695501
Position Surface form Disambiguated ID Type / Status
Subject Bodelwyddan Castle E277983 entity
Predicate locatedIn P40 FINISHED
Object Bodelwyddan E248652 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: Bodelwyddan | Statement: [Bodelwyddan Castle, locatedIn, Bodelwyddan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bodelwyddan
Context triple: [Bodelwyddan Castle, locatedIn, Bodelwyddan]
  • A. Bodelwyddan chosen
    Bodelwyddan is a village in Denbighshire, North Wales, known for its strategic location near the A55 and landmarks such as Bodelwyddan Castle.
  • B. Penclawdd
    Penclawdd is a coastal village on the Gower Peninsula in South Wales, historically known for its cockle industry and views over the Loughor Estuary.
  • C. Tywyn
    Tywyn is a coastal town in Gwynedd, Wales, known for its sandy beaches on Cardigan Bay and proximity to the scenic Talyllyn Railway.
  • D. Brycheiniog
    Brycheiniog was an early medieval Welsh kingdom located in what is now Brecknockshire in south-central Wales.
  • E. Abergynolwyn
    Abergynolwyn is a village in Gwynedd, Wales, known for its historic association with slate quarrying and its station on the narrow-gauge Talyllyn Railway.
  • 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_69d6aafe02d881909900d54ad7d4af84 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a47cef60819088b7cc3a3a711e4c completed April 10, 2026, 7:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69fd54f264d48190be636796d694ceb1 completed May 8, 2026, 3:13 a.m.
Created at: April 8, 2026, 9:40 p.m.